Calvin Austin's Blog

The unwritten story of open source java

I left Sun in 2004 after 8 fun years at Javasoft. Open Source Java was a annual discussion at Sun and in many conversations with open source advocates and companies. Many of the engineers I knew were for open sourcing Java as long as the motivation wasn't just to simply reduce headcount in engineering. However each proposal got shot down somewhere in the approval process. There were theories on how, who, why but ultimately the result was the same, at best a small compromise in the license but still no open source Java.

However competition is good, in the same way that C# ultimately made Sun continue to invest heavily in Java, the continued investment in projects like Harmony were always on the radar. In addition having a technical relationship with the IBM Java team meant that IBM used every opportunity to request Sun open source Java as every JSR lead was reminded as the defacto IBM comment in the JSR approval process was that IBM request a change in the license

Danese Cooper decided to work out the full timeline of open source Java The People Who Brought You FOSS Java as you can see its been a fairly long road and involved many people. Sun kept many communities involved including the Java champions which I have to give them full credit for, although it would have been even nicer if we could have dropped the NDA! So in closing, this is a great week, could have Java been open sourced earlier, yes but even late in Java's timeline it could be the real jolt that desktop Java needs. Do I think Java will fork?, no, maybe slightly, but nothing that would affect companies that standardize on a version anyhow.

Oh and Dalibor, I really owe you that beer now!

Comments

• Thanks, Calvin, I'm looking forward to meet you one day and then pay you back all the beers I own you!

  Posted by: robilad on November 15, 2006 at 07:14 PM

• I am not happy at all with this. Those gpl kiddies are everywhere. At job interviews for Java software developer they ask you what you think of linux (or better linsux) and now sun choice for gpl.

  If I want to use an open source Java I would choice Apache Harmony, and gpl is forbidden inside Apache, the best policy you can think of !

  Apache rulles, Sun SUCKS!!

  Posted by: carmello on November 16, 2006 at 01:19 PM

• Calvin,

  Java will not fork, simply because it is stil a TM of Sun that is protected by the JCP and the pass of the TCK to get the "green ticket". This means, that the JSR have the full controle on what is inside the TCK and what is tested... at any time they can raise the compatibility level if required ;-)

  Plus the license chosed and its viral effect when forking will preven "anticipated predators" to sing their famous song : "embrace and extend" !

  GPL of Java will mean that on medium term perspective, major platform could be "LinJa" insead of "LAMP". The arrival of PHP on Java platform (see quercus) is first sign of this.

  GPL will benefit the quality of the implementation, because Sun has not enough resources to fix all the long-lasting bugparade hits ! I am anticipating a tsunamy of contribution ... so the question is now : will sun be able to handle the validation burden of the patches review ?

  I think that at a point of time, they could be constrainted to even accept that some "top contributors" (understanding perfectly the platform and the arcanea) can directly commit on the tree. Let's see ....

  Carmelo, GPL and Apache is a known issue. I think the only reason left that could have prevented Sun from GPL Java was Apache impact ! AFAIK, there is nothing preventing Harmony to be still successfull (say if a "famous donator" and "major java player" would be kind enough to donate their SDK ) . Gimme an H, gimme an A, gimme an L :)

  Plus, from my understanding, with classpath exception, all the Apache libraries will go on to interroperate perfectly with Java. So side effect on Apache Java projectsbut Harmony.
  FYI, releasin the Sun code to Harmony is not possible because the Apache License is not viral. So it means, "anticipated predators" could go in "carnage" mode. I don't know anybody in the Java community want a fork to happen, knowing the power ot this predator.

  Rgs,
  JB

  Posted by: bjb on November 17, 2006 at 05:58 AM

• Calvin,

  We are looking for a lead developer like you to join our team! Are you in the NYC area? We are at E2CG.com.

  Best regards,
  Richard Celic
  rcelic@e2cg.com

  Posted by: e2 on November 27, 2006 at 01:08 PM

• Even as a non-technical person I enjoyed reading your article. 99% of my working day is engulfed by trying to find Core Java Developers for my client Lehman Brothers. I work directly with the Head of Global IT, as well as the Hiring Mangers in their Equities and Fixed Income Divisions.
  
  The below description (Core Java, SQL, UNIX/Linux platform), in particular, is a very cool opportunity working on a system that handles 6-10% of the New York Stock Exchange volume on a daily basis. These guys are solid, or as we call them HARDCORE! They are open to developers outside of the Financial Industry. They work hard and get paid a lot of money! All of my opportunities are full-time/permanent and a great group of guys. I have recently places 6 people in this group.
  
  Do you have any recommendations of finding some excellent java developers? I am open to paying referrals fees, and would be greatly appreciative of any ideas which you might have. We have roles in New York City and Jersey City.
  
  Senior Developer/Developer with experience developing server side applications in JAVA for a UNIX/LINUX environment. The candidate should have experience in some relational database and SQL programming, experience with network programming, Java performance tuning, and experience with developing scalable, robust, high performance systems. Experience with FIX, Exchange Connectivity and Equities a big plus. Wall Street experience is desirable. Candidates must have excellent communication skills, be highly motivated as they will be working in a fast paced/high pressure environment. Familiarity with PERL/Shell scripting also a plus. The current project involves working in Connectivity Technology group re-architecting the DMA system that currently handles 6-10% of the NYSE.

  Anyone who knows why it is recommended to set the -ms and -mx parameters to the same value for performance, and knows what the java.lang.string.intern method is a HOMERUN.

  Dorn Stewart
  ds@navistaff.com

  Posted by: wallstreetit on June 21, 2007 at 11:01 AM

This work is licensed under a Creative Commons License.