Java 16 Features | What's new in Java 16?

By -

Java 16 Features

JDK 16 is the open-source reference implementation of version 16 of the Java SE Platform as specified by JSR in the Java Community Process. 
After jdk 15 released oracle is working on JDK16 and JDK17. 

Some of the important Java 16 features are:

Java 16 Features:
JEPs targeted to JDK 16, so far

357: Migrate from Mercurial to Git
369: Migrate to GitHub
347: Enable C++14 Language Features
338: Vector API (Incubator)
387: Elastic Metaspace
386: Alpine Linux Port
376: ZGC: Concurrent Thread-Stack Processing
386: Alpine Linux Port
388: Windows/AArch64 Port

Some More java 16 features are coming up. We will discuss once openjdk Java Community Process released some information.

This release will be the Reference Implementation of version 16 of the Java SE Platform, as specified by JSR 391 in the Java Community Process.

What's new in Java 16?

357: Migrate from Mercurial to Git

Migrate all single-repository OpenJDK Projects from Mercurial to Git

369: Migrate to GitHub

Host all OpenJDK Git repositories at https://github.com/openjdk/.

Features:

Enable C++14 Language Features:

Allow the use of C++14 language features in JDK C++ source code, and give specific guidance about which of those features may be used in HotSpot code.

338: Vector API (Incubator):
jdk.incubator.vector, express vector computations that reliably compile at runtime to optimal vector hardware instructions on supported CPU architectures and thus achieve superior performance to equivalent scalar computations.

JEP 387: Elastic Metaspace:

Return unused HotSpot class-metadata (i.e., metaspace) memory to the operating system more promptly, reduce metaspace footprint, and simplify the metaspace code in order to reduce maintenance costs.

JEP 386: Alpine Linux Port

This JEP intends to integrate the Portola Project upstream.

JEP 388: Windows/AArch64 Port

This port includes the template interpreter, the C1 and C2 JIT compilers, and a limited set of garbage collectors (serial, parallel, and G1). 
It supports both the Windows 10 and Windows Server 2016 operating systems.

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk.
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();     TransportClient client = new P
Read more