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 01:26 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. Then you can control it as you like. For example take the Mono project - instead of beeing innovative and starting a solution of their own when Microsoft announced .NET they waited until .NET was huge and then just tried to "make something similar". The same could be said about Java, really.
Obviously I'm generalizing here, but that's my impression. Some of the most successful os projects I know of didn't play catch-up with proprietary software. Instead they made something of their own and know proprietary software is playing catch-up with them. A good example would probably be Apache.