Valhalla? Python? Withers? Lombok? - Ask the Architects
summary
Semicolons stay; removing them is ruled out as disruptive. Valhalla ships a minimal first JEP with a stable spec and an early‑access build expected in a month or two, followed by three more JEPs that add features like value types and specialization. GPU work centers on Project Babylon using Panama/FFI to emit CUDA/OpenCL, while Loom continues tuning virtual threads (IO polling changed in JDK22, memory optimizations ongoing). Startup improves via Leiden (evolving from CDS), NumPy‑style libs stay outside the JDK, and post‑quantum crypto appears in JDK21/Java24 JEPs.
AI-written summary · about
chapters (21)
- 0:00Introductions and T-Shirt Rules
- 1:47Getting Rid of Semicolons
- 2:39What's Next After Valhalla?
- 4:58Lombok Features in Java
- 6:36Better GPU Programming
- 9:39What's Next for Loom?
- 11:41What Decision Would You Change?
- 16:28Multiple Returns and Structural Tuples
- 19:24Quantum Computing
- 20:57Future JDK GCs
- 22:56Java vs Python
- 30:05Startup-Time Solutions
- 32:15How to Include an AOT Cache
- 35:09NumPy/SciPy/... Analogues in the JDK
- 37:47TinyPointers Hashes
- 38:53Unsigned Numerical Types
- 42:47Record Withers
- 46:15Future Footguns
- 48:32Foreign Calls Into Java
- 49:48Changes to Visibility
- 51:26Outro
related talks
57mJava Next - From Amber to Valhalla, from Loom to Leyden, from Babylon to Panama
52mValhalla - Where Are We?
50mJava Next - From Amber to Loom, from Panama to Valhalla
45mJava Next - from Amber to Loom, from Panama to Valhalla
51mValhalla - Where Are We?
46mJava Next - From Amber to Loom, from Panama to Valhalla
51mYour next JVM: Panama, Valhalla, Metropolis
45mBeyond the Hype: Unpacking the Latest Features of JDK