From JavaWorld.com, I saw this “Sun says open-source Java possible in ‘months’: Logistics such as maintaining compatibility still being worked out.”
After talking with Simon Phipps and others at Sun, maintaining compatibility and other standards does seem to be a priority, and it’s an important one at that. Standards do keep Java API and specs from getting obsolete and provide the level of security and stability that most corporations, organizations, and other developers and customers need thanks to Sarbanes-Oxley and other acts that mandate it for financials and much more.
Yes, I know, I know. Some of you are going to say that Sun is evil and all that. Look: Sun is not perfect. But neither are other open source organizations and companies out there. Each has its flaws. But I think Sun’s moves toward being pro open source, while at times questionable, are based on sound motives and intent. According to Simon at JBoss World, Sun started as an open source company of geeks. I wish I had time to go into this history, but I didn’t have the time.
But besides open sourcing Java, Sun has been heavily involved in open source Java implementations and other such as the following:
* NetBeans Java IDE and framework (soon to include Java EE 5)
* GlassFish Java EE 5 Web app server
* Jini networking
* Other Sun Open Source Java Projects
Sun also offers OpenSolaris, an open source version of Solaris with Janus for Solaris-Linux interop, contributes to projects such as OpenOffice and much more. Sun even has open source chip offerings.
Personally, I think Sun’s message is just starting to get out there. But actions do speak louder than words.
The JCP.org is not meant to be an open source community. Instead, it serves to help define, refine, and finalize standards. In terms of a Sun open source community where innovation must truly occur, I think Sun has a number of resources like Java.net, etc., but it’s a bit scattered all over.
I asked Simon about this, and what he thought of this and what was best open source community he liked. He seemed to agree that the scattering of Sun’s open source Java projects all over could be an issue. He also answered Apache.
Anyway, it sounds like Sun is really on the verge of open-sourcing Java. What do you think?
In a computerworld article, java is bringing in money for sun. why would give away the family jewels (java) when java could alleviate some of their financial troubles and them is the competitor's edge? that is business sucide
JCP primarily serves a marketing purpose in its current form, rather than serving "to help define, refine, and finalize standards".
There's room for improvement in the JCP.org - I grant you.
Ideally, I would like to see Sun involve OMG regarding Java standards.
Do you belong to the JCP, Dalibor? You would be most welcome as a member.
Just saw this now...
Sun Denies Open Source Java Imminent
http://www.internetnews.com/dev-news/article.php/3617071
Simon, nope, I'm not on the JCP, for a few reasons:
a) the JSPA legalese required to participate: too long, too NDA-ish. I want to help improve specifications. Making all the individual who'd be able to help spend their time dissecting 10 pages of dense legalese before one can help is not such a great idea. The JCP should either drop the JSPA for participating on the JSRs, or cut it down to one page.
b) unclear legal restrictions on participants in JSRs. When the call went around to join the Mustang, I asked the spec lead what the legal implications would be on me as an independant implementor, but got no real reply. If Sun's spec lead on Mustang can't figure out what the legalese means, then there is someting seriously flawed with the system.
c) most core Java JSRs are not transparent, for members and non-members alike. If I want to know what's being cooked in JSR 277, to pick an example, I wouldn't be any wiser than I am now if I joined the JCP, as the spec lead is not encouraging public participation on that JSR, within or outside the JCP.
d) JCP is currently focused on quantity, rather than quality of the specs. In particular in the area I am familiar with, Java 1.5, there are several APIs that are very poorly specified, and should have never become part of Java. Stuff like http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4350444 is rather bad in an industry standard.
I think JCP is a good idea, that's not implemented very well. For Java to prosper in the future, the JCP needs to open up majorly, and grow further than the 700 individuals and organisations that are in it today. It needs to come with full, mandated transparency on every JSR, no-strings-attached access to specifications and test suites, like W3C does. It needs to have a patent policy that requires disclosure of submarine patents embedded in specified technology, and created a patent covenant around each JSR.
It needs to make the life of Java developers easier, not harder, as it does currently.