It'll be probably even more out of date in the next few minutes or so. :) Still ever tried to compile all the Mono apps for eager Mono familiarity? PKGCONFIG > 2.8 PKGCONFIG > 3.14159268

If .NET was pure, then I would agree. But its the impurities that make it proprietory. MONO has done a good job of adapting the impurities but still some Mono apps need WINE to function. My biggest complaint about mono, is that if code written was pure there wouldn't be a problem. But as yet most Open Source projects align to various versions, and capabilities. For instance LINUX autoconfig/ configure scripts realy heavilly on the pkgconfig version numbers. After installing vanilla Mono, most of these applications fail to compile because there is no consistency in versioning between applications, and their version on MONO. Microsoft wins on consistency. However never underestimate the power of the collective. I am still eagerly watching MONO and implementing pure MONO apps. That all run on Windows. Another big pain is Microsofts low level Thread Pool implementation for Networking. If you are a Java guy and you CLR your Java code. Anything network related will behave very differently to a JVM. Performance frankly dies. Because the .NET configuration for non licienced and non Server systems, cripples the ability of multiple threads to simultaneously handle network connections. .NET patterns, are yucky in that they resemble hacking. While I appreciate the performance aspects of the patterns, they do not abstract (Meta interface) there patterns very well. You almost need a General usage Facade to make them understandable and useable.