Ted Neward writes "85 of 101 Reasons, Rebutted". In the time tested tabloid technique of using a catchy headline, he makes use of the word "rebutted". However, the word "reviewed" would have been more appropriate. Afterall, he agrees with a majority of the arguments, in fact, he further strengthens the arguments. Ted is agreement with 1, 2, 3, 7, 9, 10, 11, 16, 20, 21, 22, 24, 27, 30, 31, 32, 33, 35, 36, 43, 44, 45, 46, 47, 48, 49, 50, 51, 55, 57, 59, 60, 69, 72, 73, 74, 75, 76, 77, 78, 80, 82. That's 41 reasons out of the 85. His rebuttals are with 6, 8, 12, 13, 14, 15, 18, 19, 23, 25, 26, 28, 29, 34, 37, 38, 39, 40, 41, 42, 52, 56, 58, 61, 63, 64, 65, 66, 67, 68, 70, 71, 79, 81, 84. That's 35 reasons. The rest he's ambivalent about. There are of course, simply errors in his rebuttals, I will tackle in the final publication of the 101 list.

Here are 5 more reasons:

86. ClassLoaders

Java ClassLoaders allow bytecode analysis and manipulation, a feature absent in .NET. This runtime transformations allow for innovative interception based techniques like dynamic aspect oriented frameworks, testing frameworks and instrumentation for manageability.

87. Dynamic Proxies

Java Dynamic Proxies type safe dynamic interception of method invocations. This is extremely useful in dynamically creating remote stubs rather than using a compilation approach. JBoss uses this mechanism to allow for a more productive development environment for EJBs. Dynamic Proxies have also been used in other ways like in AOP and Design By Contract implementations. Dynamic Proxies are absent in .NET

88. More Tools To Explore The Semantic Web

RDF, TopicMap and Ontology Tools written in Java are more available to researchers than .NET. In fact, are there any RDF or TopicMap tools written in a .NET language?

89. Better Support for Emerging International XML Standards

The Jigsaw HTTP server from W3C serves as a test bed for emerging W3C standards, it is written in Java. Other W3C XML standards that have java implementations include RDF, SVG, XML Query, and XForms.

Oasis is a consortium for developing XML standards for Business, the ebXML standards are jointly sponsored by UN/CEFACT, Microsoft is conspicously absent in this standards body. Also OASIS implementations tend to be done in Java, examples are RelaxNG, BTP and Sun's JAXM. Furthermore, many oasis standards are also becoming ISO standards, an example is RelaxNG.

90. More Easily Portable Virtual Machine

Which Virtual Machine is more easily portable to a new machine? Hints to the answers can be found looking at the progress of two open source projects. Mono [ http://www.go-mono.com ] is a project that is porting .NET to Linux systems, IK.VM.NET [ http://radio.weblogs.com/0109845 ] is a project that is porting Java to .NET.

Mono started over one and a half years ago, and has a cadre of programmers and corporate funding. IK.VM.NET by contrast was started much later and is developed by a single person. In that time span, IK.VM.NET is able to run the Eclipse IDE inside .NET, in stark contrast, Mono is unable to run even the simplest of WinForms application.

The Java Virtual Machine and Java Libraries are designed to be portable, .NET libraries are simply not portable.