Open Source Java to have little impact on end-user developers

Since Sun’s announcement this week of their concrete plans to Open Source the javac compiler and the HotSpot VM, I expect there has been some panic in some circles discussing what this means for current and future Java developers and projects.

As summarized in this news item on news.com, the impact is likely to be neglible to end-user developers, and current and/or future projects using Java. The main difference will be that you have the option to commit features and/or bug fixes back to the source. In reality, a much higher percentage of users of open-sourced software just use the software as it is – only a small number ever get involved in the ‘nuts ‘n bolts’ and become code submitters.

This should be seen as a good thing for Java as it will increase choice (who’s VM implemenation do I want to use?), and through competition keep people from becoming halfhearted about their VM implementation. Even up until now there have been commercial VM implementations from different vendors (BEA’s JRockit, IBMs VM), as well as ‘based-on’ Java implementations, which for legal reasons are not allowed to call themselves ‘Java’, but are definitely based on the language (eg Waba VM for handheld devices) and even based on the Java platform such as Microsoft’s Common Language Runtime (CLR), which is arguably the same concept as the Java VM, together with the C# language and a number of other languages which can be compiled to run on the same CLR.

Sun drops ‘Mustang’ and ‘Dolphin’ Java projetc names to get ready for open sourcing Java

Sun will be dropping the project names they use for upcoming JDK releases to get ready for the open sourcing of parts of the Java platform. I guess this is to reduce confusion about what project name is what release.

So from this point onwards, the release formally known as Mustang will be called just JDK 6, and Dolphin will be just JDK 7. Both projects are already on java.net – JDK 6 is here, and JDK 7 is here.

For a small piece of Java history, check out this site which lists all the project code names for all the previous Java releases.

“Top Five Reasons to Like Glassfish” and “Could Glassfish become the next major App Sever?”

Gerrtjan has an interesting blog entry that I just came across from back in April that lists a few points that I wasn’t aware of with the Glassfish EE5 app server.

The most interesting of this points is his point #1 – ‘Glassfish is lazy’ – by this he is referring to a feature that the appserver only initializes the features you have configured and/or are using by your deployed apps. For example – if you deploy a webapp with no EJBs, only the servlet container is initialized, so you don’t pay a penalty for running small, simple apps on the server. So in this respect even if you are testing small webapps there may not be any compelling reason anymore to use Tomcat by itself?

There has been a huge amount of news coverage and blog posts on Glassfish in the past year, which prompts me to ask the question, “Where is JBoss?”. Since their buy out by RedHat they seemed to dropped off the face of the earth. Have their frequent and ‘full of themselves’ blog posts been tamed by corporate RedHat? Or do they have something up their sleeve that they have been working on that they are about to announce with great fanfare? Floyd Marinsescu on InfoQ.com is asking the question “Could Glassfish become the next major App Sever?”. Take a read of his post on InfoQ.com