Java vs .NET

CHaN_316 writes "Yahoo is running a story called 'Is Java Finished?' It provides a brief overview of the strengths and weaknesses of J2EE and contrasts them with .NET. Classic arguments are brought up like Java being great for portability while .NET ties you down to Microsoft products, etc. It's interesting that they bring up the Java Community Process, and how it is a rather slow moving procedure that is causing Java to become stagnant."

Comments

Re:Lies, statistics, and analysts

[bladernr]

You are really hitting on the biggest problem with Java: it is not a standard. Java is a proprietary technology championed by a maga-corp (Sun, in this case). How, exactly, is that different from .Net and Microsoft?

When I use C++ to write OSS for Linux, I am using a standard (C++) to write for a standard API (POSIX, X/Open). When I use Java, I am living in Sun-land. When I use .Net, I am living in Microsoft-land. I fail to see the difference.

I, for one, do not like locking myself in to a vendor-specific solution. No Java. No J2EE. No .Net (No a lot of other things, like PL/SQL, also).

A previous poster talked mentioned something like "Java vs .Net is like to big, fat, ugly chicks in a cat-fight." So true....