Please support our Software Development advertiser:
Featured Entry 
Nov 13th, 2006, 8:34 am
OK, I know that Sun Microsystems has already open-sourced the Java EE5 application server code under the auspices of its GlassFish project, but the breaking news is that the full Java source code is to follow next. Sun has announced that the Java code will be covered by the General Public License 2 (GPLv2) which is great news for all you Linux developers out there who have been less than inspired by the Sun ‘Community Development and Distribution License.’
Even more so, I suspect, because I am led to believe that Sun is to use the classpath exception license addition to allow programmers using open source Java to use a different license for their applications, preventing everything from having to be covered by the GPL. This is obviously going to be an important factor for those of you working with Java libraries and virtual machine on top of shipping applications, because it means that your current licensing will not be affected. And if you really don’t want to get into the whole open source thing, then Sun have even thought of that by running a dual licensing structure that sees the commercial license continue to be available.
One thing is for sure, this whole process of open sourcing Java which starts as form today, will help to establish the technology in the hearts and minds of web developers, like it needed any help in that direction. It will also help to increase support revenues for Sun, and that’s something they do need help with.
Expect to see Java Micro Edition move to open source licensing first, with Java Standard Edition taking up to six months to follow. It would appear that Sun are ‘not ready’ to let all six million lines of this code out into the one in one fell swoop, instead adopting a piecemeal approach with compiler, hotspot virtual machine and help system leaking out one at a time.
What will be most interesting, at least from my non-developer, technology journalist perspective, is whether this move will lead to code forking and a fragmentation of the Java user base. And if that happens, far from boosting Sun revenue and position it could well end up being a nail in its corporate coffin.
Even more so, I suspect, because I am led to believe that Sun is to use the classpath exception license addition to allow programmers using open source Java to use a different license for their applications, preventing everything from having to be covered by the GPL. This is obviously going to be an important factor for those of you working with Java libraries and virtual machine on top of shipping applications, because it means that your current licensing will not be affected. And if you really don’t want to get into the whole open source thing, then Sun have even thought of that by running a dual licensing structure that sees the commercial license continue to be available.
One thing is for sure, this whole process of open sourcing Java which starts as form today, will help to establish the technology in the hearts and minds of web developers, like it needed any help in that direction. It will also help to increase support revenues for Sun, and that’s something they do need help with.
Expect to see Java Micro Edition move to open source licensing first, with Java Standard Edition taking up to six months to follow. It would appear that Sun are ‘not ready’ to let all six million lines of this code out into the one in one fell swoop, instead adopting a piecemeal approach with compiler, hotspot virtual machine and help system leaking out one at a time.
What will be most interesting, at least from my non-developer, technology journalist perspective, is whether this move will lead to code forking and a fragmentation of the Java user base. And if that happens, far from boosting Sun revenue and position it could well end up being a nail in its corporate coffin.
This blog entry was written by Davey Winder, staff writer aka happygeek. It has received 6,060 views, 2 comments, and 28 linkbacks. 1 voter has rated this entry 5 out of 5 stars. It was promoted to featured status Nov 13th, 2006.
•
•
•
•
advertising ajax blog browser browsers business code community competition development domains firefox google hardware ibm india intel internet java linux marketing microsoft microsystems mobile mozilla news office open source opera php privacy programming red hat research rss search security software sun technology ubuntu video vista w3c web windows xml yahoo youtube
All Recent Tags Comments (Newest First)
jwenting | duckman | Nov 13th, 2006
•
•
•
•
And yes, it will lead to large amounts of forking and mutually incompatible versions all released as "Java".
Those already existed to a small degree, aimed at destroying confidence in the platform, and will now be a lot easier to create.
The userbase won't get fragmented though, as those forks will (for the most part) not be aimed at "fixing" things but destroying them and released by people who have no interest themselves in using Java but only want to confuse end users and cause them headaches when using Java software.
As it is there are tons of questions from Linux users about their Java based applications not working which are almost exclusively tracked down to them having gcj set up as their default Java runtime.
This idiotic decision by Sun will compound that problem a thousandfold in short order and drive it onto the core platform for Java as well, which is Windows.
Software manufacturers will no longer be able to rely on their users having a JVM that can run their software and will abandon Java for (for example) C#.
Those already existed to a small degree, aimed at destroying confidence in the platform, and will now be a lot easier to create.
The userbase won't get fragmented though, as those forks will (for the most part) not be aimed at "fixing" things but destroying them and released by people who have no interest themselves in using Java but only want to confuse end users and cause them headaches when using Java software.
As it is there are tons of questions from Linux users about their Java based applications not working which are almost exclusively tracked down to them having gcj set up as their default Java runtime.
This idiotic decision by Sun will compound that problem a thousandfold in short order and drive it onto the core platform for Java as well, which is Windows.
Software manufacturers will no longer be able to rely on their users having a JVM that can run their software and will abandon Java for (for example) C#.
jwenting | duckman | Nov 13th, 2006
•
•
•
•
Time to start looking for another line of work then.
Companies will pretty rapidly start moving away from Java as they want nothing at all to do (and rightly so) with anything that even remotely reeks of GPL.
Companies will pretty rapidly start moving away from Java as they want nothing at all to do (and rightly so) with anything that even remotely reeks of GPL.
Post Comment
•
•
•
•
Only community members can start a blog or comment on blog entries. You must register or log in to contribute.
•
•
•
•
•
•
•
•
DaniWeb Software Development Marketplace
Related Blog Entries
- Apple slow to patch iPhone security holes (1 Day Ago)
- 12,000 laptops lost in US airports EVERY WEEK (2 Days Ago)
- FreeRunner Linux Phone Liberated on July 4 (2 Days Ago)
- Seeing double, twice, with Matrox M-Series QuadHead GPU (4 Days Ago)
- Googlebot gets to grip with Flash (5 Days Ago)
- Apple Leopard changes spots (5 Days Ago)
- With ‘Ganymede’ Release, Eclipse Community Gets it Done (5 Days Ago)
- The ipodmechanic is sued by Apple (8 Days Ago)
- Meister 7.2 Makes Builds More Continuous (9 Days Ago)
- YASAT: Yet Another Static Analysis Tool, This One For Mac OS X (9 Days Ago)
Related Forum Threads
