>>>Can you back that up?
>>One way: look at DICE.COM how may companies looking for JAVA talent as compare to C and C++ combined, or VB?
>
>No, thats not one way to see who is playing catch up at the technical level. Available jobs is completey irrellevant. Nice try though.
If you try to look at my previous thread, I'm speaking of the crowd. Technical Level, AFAIK, MS products are not any superior at all. MS just knows how and they have $$$ to market them. Delphi for example is far superior than VB but VB has the crowd. With JAVA's growing popularity and known to be a lean and powerful tool, plus it's free, MS developed C# to prevent the extent of Exodus.

>>VFP is not a .Net tool because it does not compile to CLR.
>
>Thats not the issue. THe issue is, why does it need to, and if it doesn't, why are you so sure that it spells disaster for VFP? I'm looking for logical reasons, not just FUD.

I just answered your inquiry, as to why VFP is not a .Net tool? If your logic is that, what's happening with current and future technology does not spells disaster to VFP, fine with me. Mine is that, if it will stay as non-.Net tool, the lean VFP crowd will become leaner long term. VFPers and IT Managers attending .NET seminars and played with VS.NET BETA 2 or even BETA 1, have second thoughts continuing with VFP. Programmers tends to look at futuristic tool. Before, we always fought that VFP is better than VB, and I was one of the enthusiastic individual. Today, it's a different scenario IMO...