>The future of VFP doesn't depend on whether or not it partipates in the CLR. From my POV, it would be a gross mistake to make VFP a CLR compliant language. The mindset of some people is that "everyting belongs on the Internet/Intranet".
Who said it is? .NET CLR is not only internet/intranet thing because there is WINFORMS.

>In truth this sort of thinking returns us to the days of "Big Iron". The fundamental reason that PCs rose to such popularity is the fact that they put power into the hands of the users.
In think the case of software development is way way different in the case of PCs. How can users will continously using VFP when it is not futuristic: technology wise? It can still compete today but how about tomorrow or in the near future? Not to underestimate the role of users here but I think it is the totality of the product itself (its competitiveness) plus marketing that make it successful.