John Carroll writes ".NET develops advantages over Java". Apparently he frequently contributes to ZDNet, writing articles that promote .NET and criticizes open source.  Anyway, he presents four reasons why .NET is better than Java. 

• Standardized Configuration - A standard XML based configuration system.
• Extensible Metadata -  Meta Attributes associated with class, methods and attributes.
• Assemblies - The unit of distribution for .NET code.
• .NET Remoting - The remote object invocation library for .NET

Could these four entries be the most significant reasons why .NET is better than Java?  If it were so then there should be nothing to fear in the Java world.  XML based configuration is pretty standard for any web or J2EE development, XDoclet supports meta attributes, Jar manifests have been available for the longest time and JAXM and the new RMI support multiple remote invocation protocols. 

Carroll in his "commentary" continues to spin ECMA standardization, Rotor source code availability and Mono cross-platform support.  We all know by now that all three are Red Herrings.  Language standardization doesn't make sense if you don't include the libraries, Rotor source code can't be used for commercial purposes and the patenting of .NET api's sink Mono's legal viability.

But, Carroll isn't done, he inserts without explanation a couple more supposed advantages.  That is "streamlined" development API and tools, improved date handling, better L10n and I18n, AppDomains, ASP.NET, native code invocation, event delegates and to top it all great documentation! 

Well my retort to each one is (in the same order) "Have you seen Eclipse?", "joda", "You can compile L18n files into classes", "Classloaders can intercept byte code, AppDomains can't", "ASP.NET restricts you to one form per page and there's no equivalent to servlets", "unsafe isn't portable", "anonymous classes are more general" and "You've got to be kidding me!"