« Old Reliable Run... | Main | Blogapps 2 progress »

Java is free!

Get the Source

By now, everybody's heard the good news that Java[1] is being released under the General Public License (GPL v2), the same free software license used by Linux. A dual-license arrangement will allow Sun to continue to offer commercial licenses. Sun's Java EE implementation and developer tools, which had already been released as open source under Sun's MPL-based CDDL license are being relicensed under a triple license of GPL, CDDL and commercial licenses.

The usual "how's this good for Joe Java developer?" and "how's Sun gonna survive?" questions are coming up on the forums and blogs. The Open Source Java FAQ answers those questions very well, but here's my take. A truly free/open source Java is good for Java developers and what's good for Java developers is good for Sun. GPL is a good choice because it's truly and undeniably free/open source and the viral nature of GPL drives innovation back to the center, which prevents closed source forks of Sun's Java implementations.

So, how's this good for Java developers? Finally, Linux distros can bundle what is arguably most popular/well known, high-quality, high-performance, multi-platform and well-supported Virtual Machine there is. And that's not just good for Java developers, JRuby is starting to look pretty good too. That will result in more developers choosing the Java VM, more ISP/hosting providers supporting Java and more users using Java. That's good for Java  developers.  And and it's good for Sun -- if Sun, the ultimate experts in Java, can't make mo'money from mo'Java then I just don't know what to say.

Why is GPL a good choice? GPL and dual-licensing gives Sun the best of both worlds. GPL means Java is truly free/open source, which satisfies the free/open source community and the growing number of governments and orgs that are mandating open source. The viral nature of GPL guarantees that innovation is driven back to the center, i.e. you can modify the Java VM and redistribute it, but you must release your mods free for all under the GPL (and trademark law says you can't call it Java). And the other world I referred to? Licensees who don't want GPL can keep on licensing under commercial-friendly terms and most probably will.

So it's all good and big congratulations to all the folks who worked to make open source Java possible! 

[1] By which I mean Java(TM) technology and include Java SE, ME, EE, etc.

Comments:

While I'm happy to see Java released as open-source, I have to play devil's advocate for a moment here: Doesn't the need to dual-license remove the benefit of the GPL driving innovation to the center/preventing forks? People can make modifications and release them as GPL, but by not giving them to Sun to release as dual-license, those changes cannot be incorporated into Sun's Java releases. I guess that means using GPL will prevent anyone from withholding proprietary changes/making proprietary forks, which does remove most of the cases with monetary motivation.

Posted by Stephen Duncan Jr on November 13, 2006 at 03:54 PM EST #

I think your point "People can make modifications and release them as GPL, but by not giving them to Sun to release as dual-license, those changes cannot be incorporated into Sun's Java releases." is a valid one. I don't think that's a big issue because the resulting fork is not closed source and nobody will consider it to be "Java."

Posted by Dave Johnson on November 14, 2006 at 12:16 PM EST #

Post a Comment:
  • HTML Syntax: NOT allowed

« Old Reliable Run... | Main | Blogapps 2 progress »

Welcome

This is just one entry in the weblog Blogging Roller. You may want to visit the main page of the weblog

Related entries

Below are the most recent entries in the category Java, some may be related to this entry.