>>I like, uh, love, uh, I'm addicted to, uh slaved to, highly (meta) data driven applications, and in the current state I'm not satisfied with either VB.NET or C#. I'm aware of all kinds of other alternatives that are complimentary in the .NET platform that just might be a solution to me, esspecially if you can use classes cross language. I'd like the .NET platform to mature and provide me with more options before I do ANY attempt on porting my HUGE codebase to any other platform. Its just a matter of economics.

>How do you assess and qualify if a language is already mature or not?

Lets look at .NET. I did see significant improvements in the data handling over the years and there certainly a lot going on in this respect for future versions. As long as that happening it has not matured yet. It took up to VFP6SP3 or VFP7 for VFP to be matured.

>And if you will wait for .NET or other tools to mature to your liking before using then it will be disastrous in the end

Why?? I can't see that. Jumping .NET right now will be disasterous for the project I'm working for right now. Too much (meta) data handling on the client side. At least the LINQ and SSCE thing need to be matured. Can you explain? If its about experience? Not an issue. We work in a team. If we need .NET experience we can buy .NET experience.

>and you accomplish yet nothing because I consider VFP as a mature product that's why it's dying naturally.

???