>>>>>I'm curoius - is anyone doing any serious, long-term new development with VFP?
>>>>>The last 4 companies I worked for are all moving to C#.net.
>>>>
>>>
>>>Several other clients are thinking of, or are already in process of, converting their apps from VFP to C# (mainly).
>>>
>>>Hi Fred,
>>>What kind of projects ?
>>>Are they moving VFP network apps to WinfForms/C# or it is some other types of projects?
>>>How does it go for them ?
>>
>>The ones I'm involved with are WinForms/C# currently or just console apps. Those have no UI, just generate .TXT or .XLS files mostly for email or FTP. We're getting involved with ASP.Net for in-house web development, but I've not yet gotten into that.
>
>In the good old days we determined if a user had to wait more than 1.5 seconds for a windows application to instantiate, they would complain about “slow speed.”

I used to work on real-time systems with graphic terminals that had to have sub 1 second response times, and that was on 38.4K serial lines. The majority of that time was the serial transmission time, the data gathering and screen generation all had to take place before that.

>
>The corporate gods have determined that we should do web apps. For the last 8 years I have done web apps and the results are not too different. It can take 30 seconds or even two minutes to instantiate a web form. This is due to network, data server and intranet – internet traffic.
>
>The decrease in speed is acceptable for some reason. I have rationalized that the reason for acceptability is that all things related to the web are good! Who am I to argue? I get paid to do this! :)

Almost makes you wonder what's going on with all the computing horsepower that's now available to us. Too much "arm waving" going on behind the scenes.