Hello readers, This is the first blog on vinodluhar.com.
In this article , we will go through top 16 new features in java 16.
Java 16 is scheduled to be released on March 16. Here is a look at what changes you can expect in the release.
- 1 JEP 338: Vector API (Incubator)
- 2 JEP 347: Enable C++14 Language Features
- 3 JEP 357: Migrate from Mercurial to Git
- 4 JEP 369: Migrate to GitHub
- 5 JEP 376: ZGC: Concurrent Thread-Stack Processing
- 6 JEP 380: Unix-Domain Socket Channels
- 7 JEP 386: Alpine Linux Port
- 8 JEP 387: Elastic Metaspace
- 9 JEP 388: Windows/AArch64 Port
- 10 JEP 389: Foreign Linker API (Incubator)
- 11 JEP 390: Warnings for Value-Based Classes
- 12 JEP 392: Packaging Tool
- 13 JEP 393: Foreign-Memory Access API (Third Incubator)
- 14 JEP 394: Pattern Matching for instanceof
- 15 JEP 395: Records
- 16 JEP 396: Strongly Encapsulate JDK Internals by Default
- 17 JEP 397: Sealed Classes (Second Preview)
This Java Enhancement Proposal (JEP) will provide an initial iteration of an incubator module that can express vector calculations that are compiled at runtime. This module will be clear and concise, platform agnostic, have reliable runtime compilation and performance on x64 and AArch64 architectures, and offer graceful degradation when a vector computation cannot be fully expressed, the OpenJDK team explained.
The goal of this addition is to support C++14 language features and give specific guidance on which features can be used in HotSpot code.
This JEP relates to the goal of migrating the OpenJDK Community’s source code repositories from Mercurial to Git.
Similar to JEP 357, this relates to the goal of hosting the OpenJDK Community’s Git repositories on GitHub. All single-repository OpenJDK projects, including JDK feature releases and JDK update releases for versions 11 and later, will be migrated.
This will remove thread-stack processing from ZGC safepoints; make stack processing lazy, cooperative, concurrent, and incremental; remove per-thread root processing from ZGC safepoints, and provide a mechanism for HotSpot subsystems to lazily process stacks, according to OpenJDK.
Unix-domain sockets are used for inter-process communication, and are similar to TCP/IP sockets, except they are addressed by filesystem path names instead of IP addresses and port numbers. It is intended for Java to support all Unix-domain socket features common across major Unix platforms and Windows.
The goal of this JEP is to port the JDK to Alpine Linux and other Linux distributions that use musl as their primary C library.
According to OpenJDK, Metaspace has been notorious for using a lot of off-heap memory, so the goal of this feature is to return unused HotSpot class-metadata to the operating system, reduce metaspace footprint, and simplify metaspace code to reduce maintenance costs.
The JDK will complete its port to Windows/AArch64.
Java will introduce an API that offers “statically-typed, pure-Java access to native code.” In combination with the Foreign-Memory API, this will simplify the process of binding to a native library, which is an error-prone process.
This feature will designate primitive wrapper classes as value-based. It will also deprecate their constructors for removal, which will launch new deprecation warnings.
The new jpackage tool can be used to package Java applications.
This API enables applications to safely access foreign memory that is outside the Java heap. It was created because many Java applications access foreign memory, but the Java API doesn’t have an efficient or safe way of accessing foreign memory.
The goal of this feature is to enhance the pattern matching capability on the instanceof operator. According to the OpenJDK team, pattern matching allows common logic to be expressed concisely and safely.
Records are classes that can act as “transparent carriers for immutable data,” the OpenJDK team explained. They can be helpful with modeling data aggregates.
According to the team, this change will encapsulate internal elements by default, except for critical internal APIs like sun.misc.Unsafe. The motivation behind this strong encapsulation is that developers of libraries, frameworks, and tools often use internal elements in ways that compromise security and maintainability. Strong encapsulation ensures that code outside of a module can only access public and protected elements of a package, and that protected elements can only be accessed from subclasses of their defining classes.
Sealed classes restrict which other classes extend or implement them. They will allow the author of a class to control what code can be used to implement it, provide a more declarative way of restricting access, and support future directions in pattern matching.
Thanks for reading. Please comment, share with your friends. Have a Great day 🙂