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.
great article...
by Anonymous on Fri 10th Jun 2005 13:50 UTC

I agree ... this is one of the best thought out articles I've read in a while. Kudos. I lean on the OSS side of things, primarily more because of pragmatic reasons. I just want to install linux, or BSD and run my Java apps and not have to worry about GCJ being incomplete or something not working - and I want my clients to be able to do the same. Java has become as mainstream as c/c++ in the business world. It's time that every platform ship with a certified Java implementation, IMHO.