days
0
-58
-2
hours
-1
-5
minutes
-4
-2
seconds
-3
-7
search

#jep

Taking out the trash

JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector

A new Java enhancement proposal, JEP 363, has graduated from being a simple draft. It proposes to remove the Concurrent Mark Sweep garbage collector, which was deprecated two years ago to accelerate the development of other collectors. Let’s take a closer look at the future of Java.

Simpler is better

JEP draft: Throughput post-write barrier for G1

Java Platform Team software engineer Man Cao has published a new JEP draft proposing to improve the performance of the G1 garbage collector when concurrent refinement is disabled. He proposes to do this by introducing a simplified post-write barrier. Let’s take a closer look at what could be the future of Java.

My data types are sealed

JEP 360: Sealed Types

A new Java enhancement proposal, JEP 360, has graduated from being a simple draft. It proposes to bring sealed types to Java, allowing developers to impose restrictions on which other classes or interfaces may extend or implement them. Sealed types could work in tandem with records, which is the business of its older sibling, JEP 359. Let’s take a closer look at the future of Java.

That's got to be a new record

JEP 359: Records

A new Java enhancement proposal, JEP 359, has graduated from being a simple draft. It proposes to bring records to Java, a new kind of type declaration. Records could work in tandem with sealed types, which is the business of its younger sibling, JEP 360. Let’s take a closer look at the future of Java.

Null marks the spot

JEP 358 – Improved NullPointerExceptions

No matter how carefully they wrote their program, nearly every developer knows the dreaded NullPointerException all too well. The JVM points to the location of the problem, but not in as much detail as you might like. With JEP 358, Goetz Lindemaier and Ralf Schmelter propose a solution to this problem.

  • 1
  • 2