So, what do you think? Will this help java to get even wider adoption? Will this help projects like Openoffice.org, since now they don't have to worry about beeing dependent on sun now? And how will this affect Java versus .NET?
wasn't it open source before? i remember compiling the 1.5 jdk before there were freebsd binaries available...
>>2
Not open source as in "You can change and modify it as you like and then redistribute that.".
Nobody cares about the JDK. The only interesting piece of technology is the dynamic recompiler.
I, for one, am looking forward to seeing Java applications like Limewire and Azureus in my ubuntu repository. Those that ran to slow in gcj
I agree with >>4.
There are a lot of languages that would benefit from a port to a decent VM, but some support from the VM would be helpful.
That security model is nice too.
I don't really give a fuck about Java, but maybe now Linux distros can finally start including it and not force users to go through the most absurd procedures to get it installed.
It's not open source yet. They say "early 2007, almost all of it". Close, but no cigar -- yet.
>4
I can't help but feel that this would have been a lot more welcome had it happened before so much effort was wasted making a Free workalike for the Java API.
Indeed, I'm of the opinion that the most useful bit is the API: it will be possible to make a Java clone that's perfectly compatible, because it's actually made of Java.
Maybe RMS will shut up about Java now. And I welcome everything that will make RMS shut up about something.
It's a pretty good strategy, though, isn't it? If you're just annoying enough, peopel will do things for you just to shut you up!
>>9
History repeats itself! The Regents removed their ad clause right after GNU had finished cloning most of BSD.
I guess Sun is abandoning their CDDL license? When I saw this, I was expecting Java to be under that. It's cool news, though it would be really awesome if Sun were using a BSD-style license.
>>9
Not wasted. GNU Classpath (i.e. the FSF's reimplementation of the Java libs) is under the LGPL, which is entirely compatible with the GPL. No reason why the FSF couldn't just graft Classpath on the side of the Sun JVM, maybe replace the GNU java compiler's interpreter with the official JVM while they're at it. GIJ has been the slowest production-quality JVM for quite a while now, whereas GCJ has produced really really nice native code since five years ago.
>>13
But also no good reason they should, when the real Java API is going to be GPL/CDDL. Bad reasons might perhaps include sour grapes, and not-invented-here.
Unless there's some compelling reason to choose LGPL over CDDL.
>>14
Heh. Given the quality of typical corporate closed-source code I've seen, I think the more likely thing that's going to happen is that Sun grafts Classpath to their javur.
>>15
The Java API is source-available, just not Open Source.
And, frankly, they'd have a hard job importing all the stuff that Classpath does wrong, or doesn't yet have an implementation for ( http://www.kaffe.org/~stuart/japi/htmlout/h-jdk15-classpath.html).
>>16
Guess we're in for some interesting times come early 2007, then.
>>16
Dude, your link compares Classpath to JDK1.5. As in what Sun released with Java 5, you know the one with half-assed templates and everything.
GNU's java compiler GCJ doesn't support most of the Java 4 syntax extensions yet, let alone generics. It's a bit misplaced to complain about Classpath's java.lang.Boolean implementing java.lang.Comparable rather than the generic version (which is likely just a sub-interface of Comparable in the first place).
>>18
So you're saying that Sun is going to turn around and say 'Hey, this new version sucks. We should go back to what we were offering a few years ago; that way we can borrow stuff from Classpath'?
>>19
Maybe, maybe not. Maybe they'll say "hey, we're tired of maintaining this overgrown heap of barely-past-prototype library code. You seem to have a pretty good set of replacements; how about we slap those together since they're license compatible as of early 2007?". I don't know. It seems pretty certain that the two won't remain separate, and Classpath has pretty good momentum to itself already even if Sun didn't pony up the library source.