[link|http://www.javalobby.org/pdf/clr.pdf|CLR Cross Language shortcomings] this article contains rebuttal comments from the Microsoft Program Manager for the CLR, so the article is quite balanced. At the end there is a page relating specifically to Eiffel.

The bottom line is that even Microsoft [link|http://research.microsoft.com/~emeijer/Papers/CLR.pdf|admit] "It would be unfair to state that the CLI as it is now, is already the perfect multi-language platform. It currently has good support for imperative (COBOL, C, Pascal, Fortran) and statically typed OO languages (such as C#, Eiffel, Oberon, Component Pascal). Microsoft continues to work with language implementers and researchers to improve support for languages in nonstandard paradigms"

It is clear that dynamic languages will suffer under .NET.

One last quote from the article regarding Python "ActiveState reported their experience implementing Python for .NET (with funding and help from Microsoft): [link|http://www.activestate.com/Initiatives/NET/Research.html|http://www.activest...esearch.html]. The paper even reveals some cross-languages problems that I wasn t aware. They conclude the project was a success because they could get Python working on .NET; but this is with severe problems of interoperability and performance. The speed of the current system is so low as to render the current implementation useless for anything beyond demonstration purposes. Some issues are related to the immaturity of the current Python for .NET system, but many others are limitations of the CLR. Of course, Python is not a close relative to C#. This might change, as ActiveState mentions the possibility to introduce changes such as static type declarations I sincerely hope this is not the first step to make Python yet another C# skin ."