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.
by Eric Martin on Thu 9th Jun 2005 22:00 UTC

Losing any control of java might hurt $$$ pocket. Example of losing dollars is that some might lose interest in buying Sun tools.

Let me say this about java performance before anyone bashes . If java had gone with a pure interperator and a choice of a real compiler to native code instead of bytecodes with VM then I think lot wouldn't be critical of java performance and startup time. I don't think people understand the java byte code compiler and time it takes. Nobody complains of python or perl performance. They are both real snappy because of no need to compile to bytecodes.

Example of interperator and true c compiler is Euphoria. It's kind of like C.