Linked by Andy Roberts on Thu 9th Jun 2005 20:58 UTC
Java The recent announcement from Apache regarding their plans to embark on their own J2SE implementation called Harmony has re-ignited the long-running Java/OSS debate. James "Father of Java" Gosling reacted in an unexpected way by giving a misleading view of what open source is really all about. Now that the dust has settled a little bit, it's time for an article that is not championing the cause for the relicensing of Sun's implementation under more permissive, open source terms, but simply a look at what could (and could not) happen under the open source model.
Permalink for comment
To read all comments associated with this story, please click here.
Its very simple.
by Anonymous on Sat 11th Jun 2005 03:45 UTC

Sun won't provide the following:

Java integrated and distributed with free OSes and their packaging tools (e.g. apt-get install java)

Timely releases of Java compiled for new architectures (e.g. x86-64)

Java for platforms it doesn't see as relevant (Linux/PPC)

Java language compilers which produce native executable code (e.g GCJ)

Supported Java bindings for their own desktop technologies (i.e. GNOME)

GUI application libraries that provide good speed

Desktop integration and interoperability functionality.

and the list goes on.

Basically, while they seem to have this idea there are no holes in what they are offering, but the reality is they have done an awful job of making Java a good choice for anything.

They profess not to understand what they dont provide, when anybody who has ever used Java as at least one big complaint, and most people can make a much bigger list than that.

Will open source make it better? I don't know, but I'm all for them trying to do so, because Sun clearly doesn't want to.