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.
RE:os Java
by Anonymous on Fri 10th Jun 2005 11:46 UTC

Obviously so that they can provide interoperability and leverage mindshare. Implementing popular tools to reap the benefits of popularity. Reusing existing work instead of reimplementing the wheel.

It's not as if because Mono or free Java implementations exist, that everything else that isn't Mono or Java doesn't. There are more projects that aren't Mono or Harmony, so what exactly is your point?

All of this "innovation" nonsense that is constantly repeated is kind of stupid. Most things aren't innovative. Being innovative isn't some mystical inherit asset that makes what you're doing valuable. I'm creating a never before seen pile of no one gives a crap! Come one and come all!