>That's a good question, and one I've never asked any of them, although a large number still work on Fox apps.
>
>>I have to say that the further I get into .NET 4.0 ( the VFP 6.0 of .NET <g> ) the more I "get" why the strategy to move from COM and GDI made good sense. I think what a lot of our Fox community misses is that there were a lot of reasons besides its imminent demise why many top level Fox developers migrated to .NET over the last ten years. I'd be interested to know how former successful VFP developers who have made the transition to successful .NET developers would feel about going back to the VFP paradigm even if VFP were a supported product at MS.
I guess a similar question is : assuming the same level of acceptance on the part of the client (including the inhouse IT people) , beginning a new LAN desktop application for a Windows environment today ( trying to keep the playing field somewhat level ) would you use VFP/DBF, VFP/SQL or .NET 4.0/SQL ?
Assume a large, complex application, either and individual or team development. Consider the developer experience and the cost/time of development.
To me, it isn't even a close call.
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
