Java JDK 10: What new features to expect in the next Java

Download Click Here

On February 12, 2018, the planned Java Development Kit 10 upgrade got its first release candidate. A second release candidate is due by March.

When JDK 10 will be released

JDK 10, an implementation of Java Standard Edition 10, is due for production release on March 20, 2018. Key improvements proposed include a local type inference and a “clean” interface for garbage collection.

Oracle has set a six-month release cadence for Java releases. There had been plans to name this upgrade and successors based on the year and month of the release, with the first release to be called Java 18.3. But those plans were scrapped after objections were raised.

New and improved features in JDK 10

Key features expected in JDK 10 include:

• Docker awareness. When running on Linux systems, the Java Virtual Machine (JVM) will know if it is running in a Docker container. Container-specific information—the number of CPUs and total memory allocated to the container—will be extracted by the JVM instead of it querying the operating system. (The number of CPUs available to the Java process is calculated from specified sets, shares or quotas of processors.)
• Three new JVM options, to give Docker container users greater control over system memory.
• A bug fix to correct the attach mechanism when trying to attach from a host process to a Java process that is in a Docker container.
• Shorern startup times for the jShell REPL tool, particularly when a start file with many snippets is in use.
• New APIs to better enable creation of unmodifiable collections. The copyOf,Set.copyOf, and Map.copyOf methods create new collection instances from existing instances. New methods toUnmodifiableList, toUnmodifiableSet, and toUnmodifiableMap were added to the Collectors class in the Stream package, allowing the elements of a Stream to be collected into an unmodifiable collection.
• A local-variable type inference, to enhance the language to extend type inference to local variables. The intent is to reduce the “ceremony” associated with coding while maintaining a commitment to static type safety.
• A clean garbage collector interface to improve source-code isolation of different garbage collectors. The goals for this effort include better modularity for internal garbage collection code in the HotSpot virtual machine and making it easier to add a new garbage collector to HotSpot.
• Parallel full garbage collection for the G1 garbage collector. The intent is to improve worst-case latencies by implementing parallelism.
• Enabling HotSpot to allocate the object heap on an alternative memory device, such as an NVDIMM memory module, specified by the user. This feature envisions that future systems may have heterogeneous memory architectures.
• Enabling the Grall Java-based just-in-time compiler to be used in an experimental fashion on the Linux/x64 platform.
• Consolidation of the repositories of the JDK forest into a single repository, to streamline development. The code base until now has been broken into multiple repos, which can cause problems with source-code management.
• Application class-data sharing, to reduce the footprint by sharing common class metadata across processes. Startup time is improved as well.
• Thread-local handshakes, for executing a callback on threads without performing a global VM safepoint. Individual threads could be stopped instead of either all threads or no threads.
• Provision of a default set of root certificate authority certificates in the JDK. The goal is to open-source root certificates in Oracle’s Java SE Root CA program to make OpenJDK builds more enticing to developers.

Source : Click Here