>>After I've drawn the conclusion, I've decided to wait. Not that I've currently got time to do anything else than VFP development. I've got much more on my plate than I can handle anyways. And I don't see that change in the comming 4 years anyways.
>
>I agree totally. .Net is another example of MS's moto that the more complex you make it the easier it is use. Complexity does not equal simplicity. eT and others developing new languages for .Net, may help in making developing in .Net much easier and faster.
>
>Besides, it is my belief that one of the true cool features of .Net is the fact that the language the application is written in is irrelevant. They all compile to the same execution code. Mix and match languages. Use the right tool for the job. Use C# for tight, fast code, J# for those complex math problems, and possibly eT's Fox for data-centric solutions.

Actually, I'd expect them to compile into very different code, compiled for the same runtime. It would be interesting to have any sort of comparison somewhere down the road, to see how constructs in various languages compile into IL, where are the strengths of eachand where are the weak points etc. For compilers aren't made exactly equal, they must have some qualities and limitations of their own.