SQL Zone is brought to you in partnership with:

Dr. Axel Rauschmayer is a freelance software engineer, blogger and educator, located in Munich, Germany. Axel is a DZone MVB and is not an employee of DZone and has posted 246 posts at DZone. You can read more from them at their website. View Full User Profile

Java News Flash! Oracle Lays Out Java 9, 10 Roadmap

  • submit to reddit
Quoting “Java won't curl up and die like Cobol, insists Oracle” by Gavin Clarke for The Register:

Java 9 and 10 will tackle big data, multi-language interoperability, cloud and mobile and ship in 2015 and 2017 respectively, Oracle said Wednesday.

For the Java Development Kit (JDK) 10 or after, a fundamental change is being discussed: making the Java language Object Oriented. This might see the introduction of a unified type system that turns everything into objects and means no more primitives.

Features of JDK 8, due next year:

  • Faster JavaScript engine “Nashorn” replaces the existing “Rhino”.
  • Module system “Jigsaw” will make installations smaller, because one only installs those parts of the system that are actually needed by applications. That enables a risk-free way of virtually getting rid of old and deprecated parts of the Java API.
  • Support for mobile devices. Quote:

    JDK 8 will see the Standard Edition of Java (Java SE), which is built for the desktop, updated to run on the kinds of mobile devices that would currently run Java Mobile Edition (Java ME). Oracle believes multi-core and availability of hundreds of megabytes of memory on chips used in smartphones means Java SE can now run on such phones instead of just the desktop.

    Note that with Android, there already is a Java-based mobile platform. But Oracle’s desktop APIs (including Java FX) could make cross-platform development easier.
Published at DZone with permission of Axel Rauschmayer, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)



Jonathan Fisher replied on Mon, 2012/03/19 - 11:28am

How about breaking backwards compatibility? A clean SDK would be nice, free of the tyranny of the checked IOException. How about getting rid of j.u.Date, j.s.Date, and thousands of other worthless classes? Java is less elegant than other languages merely for the fact that it's SDK is antiquaited.  When you see a comparison to Ruby, they say, "Look how easy it is to say hello world." This gap could be closed by refactoring the base sdk and a heavy fat trimming. Would it break old applications? Yes, but why the hell would you 'upgrade' if you don't intend to take advantage of the platform?

Anthony Goubard replied on Mon, 2012/03/19 - 12:59pm in response to: Jonathan Fisher

It won't happen. You just have a few KB of deprecated methods in Java. You have a few MB of unused API. Do you know how many programs use j.u.Date? well, a lot.

You upgrade for performance, security issues and new APIs. Thanks to their compatibility test, after the upgrade almost everything work. No need to buy new software and no need to wait for a new version of a library to use the new platform. 

Jonathan Fisher replied on Mon, 2012/03/19 - 2:48pm in response to: Anthony Goubard

The investment companies have won't evaporate. The existing SDK can be frozen, and the two platforms will simply share the JVM. Intentional fragmentation? Yes, but it will keep Java from fading into oblivion; Java will stay current with the needs of programmers and business.

Project Jigsaw would go a long way to help this goal: the 'old sdk' could be a module that your legacy programs could require.

Loren Kratzke replied on Tue, 2012/03/20 - 6:55pm in response to: Jonathan Fisher

It will take more than java.util.Date to drag Java into oblivion, and fragmenting it for a nicer Hello World might not be a good idea.

What really frosts my cupcakes is Oracle's total inability to serve a simple but important web page. This page is supposed to serve critical vulnerability and patch information, but instead serves an error message.


The link is from this page: http://www.oracle.com/technetwork/topics/security/javacpufeb2012-366318.html

After logging in (of course, we MUST log in, how can we not be logged in...) you will see this:

Failure of server APACHE bridge:


No backend server available for connection: timed out after 10 seconds or idempotent set to OFF.

 Try to find a link anywhere on the site to report this broken functionality. The only links are to sales staff that want to know what your organization is running, etc.

Now THAT in my opinion needs fixing. This is not the first time I have seen this message. In fact since Oracle bought Sun, links to vulnerabilities and patches give you ONLY this message. Sigh...

Andy Till replied on Thu, 2012/03/22 - 4:59am

I'm quite worried about what this unified type system actually means.  On the face of it, it could mean that the following code:


Compiles to:





int no longer is usable and everything is an Integer.  All seem pretty weird or unperformant, except maybe the second option.  Oracle need to clarify what they mean by a unified type system.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.