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.
Open source solutions
by Anonymous on Sun 12th Jun 2005 23:49 UTC

Call me ignorant, but what I don't get is why does the oss community focus so much on existing (mostly proprietary) software solutions instead of innovate and make something of your own.

The open source community has built one. It's called Python. But that doesn't run the code that was written for Java, nor does it run the code that was written for .NET. The open source community has an alternitive for asp as well. It's called PHP. The only reason you keep hearing about the compatibility projects is that the proprietary owners of the originals have fairly deep pockets to dig into for advertising and name recognition. However, unless you have a real need to use one of those kits, it would seem better -- in my opinion -- if you were to use one of the totally free stacks.