>>The difference is that C# will be around 5 years from now.
>
>WIll it? Maybe they won't support the version of C# you're comfortable with now for some reason. It really sucks being dependent on Microsoft for this stuff, doesn't it?
>
>That's why it's inevitable that all development will eventually be Open Source. No one wants one company(Microsoft) calling the shots for software development based on bolstering their bottom line. No doubt corporate america will decide this in the near future too (as the federal government and most schools and universities have already)
>
>The core of VFP is solid and that's a good thing. The rest can be supported by the Open Source community as an open source project (take a look at the CodePlex vfp projects). Maybe one day VFP will be looked upon and respected as a new kind of Open Source language with a status similar to what PHP has today.


Microsoft hinted very loudly that VFP was going to end for a decade before they killed it. They gave the final target date 2 years in advance. They gave alternatives.

Those who did not take the hints and timetables were either deluding themselves or must be comfortable with dwindling maintenance assignments, as that is the only future for VFP.

VFP was a first rate tool.

.NET is easily a decade ahead in built-in capabilities. There is a learning curve (just like for VFP). The learning curve is very steep if you go after ASP.NET. The learning curve is fairly easy for Windows forms. Learn it, learn somethig else, or live on the leftovers. Get over it.

How many people are learning to be VFP programmers this year?