The Java 9 release postponement may come as little surprise to the Java community given the JDK’s track record of tardiness. But what exactly is causing the hold-up? And does this mean more time for more language features?
Oracle cannot meet expectations for the planned release of Java 9 in September 2016. In a message broadcast to the community via mailing list, chief architect Mark Reinhold has revealed that the modularisation work in Project Jigsaw needs more time.
How does Java 9’s modularity compare to the OSGI module system? Is it good to set goals for code coverage? The latest Thorben Janssen brings us the latest news and essential reading from the Java world.
Alex Zhitnitsky looks at the creation of meaningful benchmarks with the Java Microbenchmarking Harness – a powerful component of the OpenJDK code tools project that has been used extensively during Java 9 development.
You’ve already been acquainted with JAR hell, but what about the horror that may be unleashed by Project Jigsaw in Java 9? Nicolai Parlog takes a look at the possibility of Module Hell, with version conflicts and complex class loading the likely victims.
Following last summer’s announcement that the JDK’s source code would be modularized by Project Jigsaw, Chief Architect Mark Reinhold has now given an insight to the latest developments in the modularization of Java.
Among the few truly new features recently confirmed for Java 9 (alongside Project Jigsaw’s modularity) is a Java Shell that introduces the first REPL function to Java. Java Executive Committee member Werner Keil explains how Java’s new REPL got started and what it’s good for.
With Java 9 on its way, the more information you have, the better. Nicolai Parlog dissects the upcoming Project Jigsaw and inspects each feature, from dependency management and optimisation to encapsulation.
Nicolai Parlog highlights another big change coming to Java in the form of Project Valhalla. How far along is it development-wise and what challenges are there in the lead up to release?
Mark Reinhold has proposed a compromising solution for the treatment of the Unsafe class in Java 9. To find out exactly what this compromise will mean, and whether it can really dispel all doubts, we’ve enlisted the help of Hazelcast’s Christoph Engelbert.
Oracle’s Mark Reinhold has delivered a solution of sorts to the debacle that is Java’s Unsafe class. In a proposal shared via the OpenJDK mailing list, the majority of the JDK’s internal APIs would be encapsulated as part of the overall modularisation effort for Java 9.
Christoph Engelbert is back to talk more about Java’s Unsafe class and the effect it will have on Hazelcast and its customers. As we’ve seen over the last couple of weeks, this issue is still contentious and developers are still looking for answers.
The buzz around the plan to remove Unsafe from Java 9 has yet to subside, so we spoke to Technical Evangelist at Hazelcast Christoph Engelbert and founder of the Performance Java User’s Group Peter Lawrey about consequences and solutions.
The sun.misc.Unsafe API, which is used by many libraries and frameworks, is being removed as default from Java 9. With the debate still brewing, we asked Lucene developer Uwe Schindler for his opinion on this controversial decision.