Listen to the article Java SE 6 Update 10 is Officially Here as MP3
What’s special about the 6u10 that a minor release gets this much attention? After years of failures in the client space, this release is promising to reverse that trend. The message was clear; the release number maybe minor but the changes are major.
To drive the point home, Danny’s first statement was that this release is about supporting rich client content much better than what we’ve come to expect. To this end, this update has had a major overhaul of its runtime environment. The JDK has been in beta for about a year and in that time it has been downloaded more than 1,000,000 times. Most notability, this version of the JDK will be the oldest to be accepted by Google’s new browser Chrome.
In addition to the hundreds of bug fixes, the 6u10 is being touted to be lighter and more nibble full of features that create a more consumer friendly experience. Another concern was necessary support for JavaFX.
One of the biggest changes comes with the new WebBrowser plugin, Unlike the old plugin, the new plugin runs outside of the browsers process space. The advantages of moving the JRE to run out of process are numerous. The biggest is increased stability. The coolest that you can now drag your applets out of the browser and have them continue to run even after the browser has been shutdown.
Applet startup time is improved with the new plugin. The old plugin started the JRE in the browsers main event thread. WIth the JRE running out of process, the even thread is no longer tied up. The bad news is that the new plug-in is targeted to more modern browsers such as IE 7 and FireFox 3.0.
One of the biggest headaches is how Java has been traditionally delivered to the end users. This has all changed with this version of the JRE. Updates from the browser will happen more automatically without much interactions with the end user. In addition, the JRE has been broken down into a kernel, core classes to Java Plug-In and Java Web Start, and other commonly needed client side APIs. All other bits of the JRE will be downloaded in a low priority background thread. The net effect is that a clean install of the JRE has been reduced to 4 megs.
In addition future updates will be delivered via a patching mechanism that eliminates the need to download the entire JRE.Other performance enhancements include a mechanism that attempts to keep the disk cache hot with the JRE. This can result in a significant decrease in startup time.
Graphics has also been greatly improved with the introduction of Nimbus, the eventual replacement to (still the default system) Ocean. In addition to giving widgets a more modern look, Nimbus signals a switch away from raster to vector graphics. This reliance will allow graphics to perfectly adapt to future higher resolution monitors.
If with all this news you are feeling like an orphaned Mac user or Linux user, that feeling isn’t going to get better any time soon. While one from Sun or apparently from Apple, can speak for when the 6u10 may make to Mac land, recent history has demonstrated that we could be waiting for some time. The big sticking point with Linux is the need to integrate the XRender pipeline. Until 6u10 is released to OSS, that can’t happen.
Even with these hickups, the future of the platform on client machines looks bright. My measure will be when I stop getting Java install questions from my mother. Until then, we can only hope that the realization is as good as the dream.
Labels: Java, JDK6