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.
The biggest threat from open sourced java
by Anonymous on Sun 12th Jun 2005 11:36 UTC

Losing Apache web server.

Apache foundation better stick to their knitting before we find ourselves having to buy IIS or Websphere, or whatever.

The real problem with OSS is follow through -- sticking with a project. You see this everywhere you look with Linux -- broken, poorly maintained, drifting projects. The 'new' project is always better than the old, so the old one just decays.

Hello, Mozilla/Firefox -- how many developers do they have left, 6, 8, 5, 2? OpenOffice?

IMHO, java is just fine where it is, as it is, I would rather we have one working free version of java than 5 half working implementations. At least we can all bitch at Sun when java breaks and have some resonable expectation they will fix it.