Java Next - From Amber to Valhalla, from Loom to Leyden, from Babylon to Panama
summary
Six JVM efforts move from research to usable tech: virtual threads are largely delivered and JDK 24 removes object‑monitor pinning; structured concurrency and scope values remain in preview. Project Panama finalizes the foreign memory and foreign function API in JDK 22 while the Vector API stays in incubation. Leyden adds an AOT cache and class linking (JEP 483) with reported startup gains up to ~40% and a Spring PetClinic cache ≈130 MB; early AOT experiments show larger (≈70%) improvements. Valhalla, Babylon and broader Amber work continue as previews or early stages.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 1:13Six major OpenJDK projects
- 2:36Panama deep dive
- 9:54Panama timeline
- 16:34Loom motivation
- 25:18Virtual threads benefits
- 35:14Structured concurrency
- 40:23Leyden for faster startup
- 49:23Leyden limitations
- 52:32Valhalla and initiatives
- 55:27Amber and Java evolution
- 56:30Resources
related talks
46mJava Next - From Amber to Loom, from Panama to Valhalla
47mJava Next - From Amber to Loom, from Panama to Valhalla
50mJava Next - From Amber to Loom, from Panama to Valhalla
45mJava Next - from Amber to Loom, from Panama to Valhalla
51mJava Next - From Amber to Loom, from Panama to Valhalla
21mJVM Language Summit 2023 Keynote
45mBeyond the Hype: Unpacking the Latest Features of JDK
42mJava, Today and Tomorrow