One thing to remember. Sun went into a tizzy over it. This doesn’t mean that the Java community did. Vendors? Sure. Users/Developers? Only some.

Developers just want to get their work done so they can go home at 5pm :) Many people liked the Microsoft JVM.

The reason not to use the CLR is that on some projects you want to use Spring, Hibernate, [insert other technology here] but you also want low level access to Microsoft components since you know you are going to be on that platform.

Or, you could be writing code which will be shared, but you can abstract out that low level stuff and have a factory which returns Microsoft stuff, Linux stuff, Mac stuff, depending on the platform.

Dion

Now I find that statement amazing. I was floored when I heard it come out. And I don’t mean this in a sarcastic way (ok, maybe a little bit ;-) but isnt that exactly what MS did with the MSJVM oh so many moons ago and the Java community went into a tizzy over the whole thing? I know some of the frenzy was whippped up by the rancor between Sun and MSFT, but I know many Java advocates that took MSFT to task for “tainting Java” by extending it to work better with Windows. Isn’t that the same thing that you (and others) are now advocating?

Again, just an interesting sea change if that is indeed the current thinking. It of course, begs the question, why not just use the CLR if you need those things?

Just wondering since I thought it was a very interesting view point, especially if common among Java developers.