How JEPs Drive Java's Evolution
summary
Explains how JEPs move from draft to candidate to targeting a JDK release, with concrete gates: draft needs reviewers, candidate gets a three‑digit number, target implies integration work and clocked six‑month releases. Gives concrete examples: JDK 26 ships ~12 JEPs (HTTP client adds HTTP/3), a real prototype for virtual threads that runs 10,000 then 10 million threads in JShell, and removed the applet API after a deprecation sequence tied to the new FFM replacement for sun.misc.Unsafe.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:23Purpose of a JEP
- 10:04The JEP State Machine
- 17:20Alex' Role
- 26:54Tracking Removals
- 35:09In James Gosling's Footsteps
- 37:32A JEP's Style & Mark Reinhold's Role
- 43:54The Structure
- 53:55The Guardian of the JEP Process
related talks
15mJEP 493 this new Java feature is validated
39mFrom Idea to IDE - How Java Features Are Considered, Designed, and Shipped
13mJEP 49.3 - This New Java Feature Is Approved!!!
26mJava Community Participation and Collaboration
53mJava 23: Hot JEPs
43mHow to Participate in the Future of Java
38mJava 20: Reviewing the Enhancements in the Latest JDK Release
27mModern Java: Change is the Only Constant