6 ms·
> Freeing Java with the GPL was an amazing move by Sun and kudos to everyone who made that happen. But due to recent legal rulings (and assuming they don't get
by Someone1234 11y ago
> Freeing Java with the GPL was an amazing move by Sun and kudos to everyone who made that happen.
But due to recent legal rulings (and assuming they don't get overturned in the supreme court) Oracle has effectively locked Java back down. Even if it is GPL, Oracle has managed to copyright the APIs themselves, making the GPL-ness of the Java codebase more or less meaningless.
Sun did make Java free, no doubt about that, but under Oracle it is hard to argue that Java remains free. It is an Oracle product that Oracle owns, and if you try to fork it you will be sued (Oracle has made that point abundantly clear).
To be honest the GPL is now inadequate against this new type of copyright enforcement.
- narrator 11y agoIANAL, but it seems to me that Java 1.6 is GPLed and the implementation contains the interfaces. As long as they stick to JDK 1.6, which is good enough, they're fine.
- FigBug 11y agoIsn't the issue that Google didn't fork it, but instead re-implemented it and the re-implementation had Oracle code in it? If Google had forked it and kept their version under the GPL they would have been fine.
- pron 11y agoI don't think you understand. That APIs are copyrightable means that the GPL applies even to the API. The GPL does not allow any further restrictions, and Oracle isn't imposing any. You may do with OpenJDK as you please as long as you comply with the GPL. You may re-implement the APIs, or use HotSpot's JIT to compile Brainfuck bytecode -- anything at all. That doesn't mean you can use the trademark Java for the result, but that's beside the point (and applies for all open-source projects). If you don't want to comply with the GPL and you still want to build an implementation of Java -- which is what Google did -- only then do you have to comply with Oracle's alternative licensing, which forces you to make your implementation fully compliant (Android isn't) and places further restrictions (such as the use on mobile devices). In any case, whatever applies to Java applies to any other GPL project. As to Oracle suing you if you fork Java (and not abide by the GPL), let's just see what actually happened there: 1/ Google reimplemented Java not under GPL 2/ it did so while breaking compatibility, and 3/ to directly compete against what was then on of Java's main sources of income. So, yes, I think it's safe to say that if you make an incompatible implementation of Java to directly threaten Oracle's business, they will sue you. I have a feeling that other companies would do the same.