He writes:
Back to the .NET analogy: It's a product. Swimming upstream. Albeit a product with up to $50 billion of cash to make butterfly ads for it. However, it's still just a product. Once Java took hold, there wasn't a lot of room left for products in the same space. All of a sudden, Microsoft is faced with a seemingly unstoppable tide, representing the same type of leverage that commodity hardware gave Microsoft in the operating system wars against systems like Unix running on proprietary hardware.
...
So what benefit does another proprietary product like .NET provide? One that doesn't exist out of necessity, but out of the least darwinian of capitalistic circumstances? It's like a five year plan in the former USSR: You know it doesn't actually make sense or help anything, but if you live under it, you're certainly not going to say anything negative about it. And heck, this five year plan is as good as any that came before it.
when .NET began java had a lot of pros but Sun has not really been able to provide the leadership required to move java to the next level. As a result earlier anti .NET rants were credible, todays rant are almost always sensational cliches that refuse to address the fact that java hasn't moved forward for the past 3 years. Tiger is really a .NET catchup/clone
look at some of the promised features
Generics - Provides compile-time type safety for collections and eliminates the drudgery of casting.
Enhanced for loop - Eliminates the drudgery and error-proneness of iterators.
Autoboxing/unboxing - Eliminates the drudgery of manual conversion between primitive types (such as int) and wrapper types (such as Integer).
Typesafe enums - Provides all the well-known benefits of the Typesafe Enum pattern (Effective Java, Item 21) without the verbosity and the error-proneness.
Static import - Lets you avoid qualifying static members with class names, without the shortcomings of the Constant Interface antipattern (Effective Java, Item 17).
Metadata - Lets you avoid writing boilerplate code, by enabling tools to generate it from annotations in the source code.
while they are realistically becoming more developer focused, they still have that elitist attitude though java is less OO than C#. Java is still an unstandardized, cross platform (the dumbest thing to ever come out of the tech industry), unpredicatable and disturbingly unpromising technology. It made sense briefly back then, but today the only people that say it rocks are the over payed developers that benefit from the current confusion. Sun's failure at driving the technology also meant that the open source community has carried java so far despite Suns very "open" source licenses . At least LAMP is quickly providing practical andnon confusing solutions for the folks that do not want to spend money on software licenses. I always wonder why the f@#* any one would want to do a java solution of any type today, on the desktop its very broken, on the server its expensive since the developers cost so much ..........
at least now we understand why those folks are so religious about java, they are the only people cashing in,
them at stores around my house, at least 
Posts
