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.
Java should well stay under SUN control
by St Michael on Thu 9th Jun 2005 21:34 UTC

I have been a Java developer for a couple of years and
i do not see the need for opensource Java. Most opensource
developers carry the Midas touch, only that whatever they
touch turns to shit. For all these years, i could trust
the SUN Java class library to be tested, well documented
(surprise surprise) and industry proven.

The Apache fanboys may well try to do whatever they want
and they will probably implement another half-baked, buggy, monstrosity project (like most of their Jakarta output,
what a mess) that will go nowhere. Their only hope is
that a commercial company may pitty them and throw them
some code.