Your next JVM: Panama, Valhalla, Metropolis
summary
Roadmap shows concrete pieces: Project Panama provides direct up‑calls, down‑calls, off‑heap typed access and a JExtract binder workflow that turns a C header into ~6 KB of Java metadata and runnable interfaces with direct optimizable calls; Intel-backed vector intrinsics land as an Asm‑style method handle. Project Valhalla adds flat value types (Q types), parametric polymorphism (five prototypes so far), per‑species generics and U types to unify primitives and objects. Project Metropolis prototypes running the VM on Java via Graal and AOT/Substrate experiments to replace C2 and shrink C++ surface. Fibers replace heavyweight threads for massive concurrency.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:48What should the JVM look like in 20 18 years?
- 7:09Forecasting is hard
- 16:46Proiect Panama - what comes after JNI
- 19:17Big Idea: Java-on-Java
- 21:26Project Metropolis: City of Tomorrow
- 27:13Fibers Dinosaurs as draft animals, not pets
- 29:18Big Idea: Value types - Project Valhalla
- 31:43Big Idea: Parametric polymorphism
- 32:48Parametric polymorphism is hard
- 34:12Impact of parametric polymorphism
- 34:54JVM template classes and species
- 37:01Stack reification (introspecting the thread)
- 37:38Length polymorphism
- 39:42What's in a constant
- 42:51Lazy boilerplate methods
- 44:04Immutability
- 48:43Sealed interfaces: Better information hiding
- 49:19Sealed fields: Better mutability
related talks
49mJVM in the Age of AI: Babylon, Valhalla, TornadoVM and friends
46mJava Next - From Amber to Loom, from Panama to Valhalla
57mJava Next - From Amber to Valhalla, from Loom to Leyden, from Babylon to Panama
45mJava Next - from Amber to Loom, from Panama to Valhalla
50mJava Next - From Amber to Loom, from Panama to Valhalla
47mJava Next - From Amber to Loom, from Panama to Valhalla
52mValhalla? Python? Withers? Lombok? - Ask the Architects
47mBeyond the Event Horizon — What Awaits Us in Java 10