Amber, Loom, Valhalla
summary
Overview of concrete changes and how to use them: Amber adds record and sealed-type deconstruction so switch and instanceof accept nested and unnamed record patterns (record patterns remain preview; nested/unnamed aim for JDK 21), plus compile/runtime exhaustiveness checks. Loom delivers virtual threads that start in ~1 microsecond and use hundreds of KB today (target tens KB), enabling million virtual threads on a laptop, structured concurrency to replace complex CompletableFuture code, and scope values for immutable, non-thread-bound context. Valhalla brings value classes inline and user-defined primitive types with non-null “bang” arrays to get primitive-level memory and speed while keeping rich modeling.
AI-written summary · about
chapters (18)
- 0:00Start
- 6:05Amber, Loom, Valhalla
- 7:36Amber: Records
- 14:37Amber: Sealed Types
- 19:33Amber: Pattern Matching
- 21:28Amber: Type Pattern
- 22:06Amber: Record Pattern (prev 20, 21?)
- 25:00Amber: Switch Expression +
- 28:46The Unnamed Pattern (prev 21?)
- 30:25Pattern in the for each statement (prev 20)
- 31:56Amber: the Future of Pattern Matching
- 35:07Loom: Virtual Threads (prev 19, 20, 21?)
- 39:40The Travel Agency Example
- 40:14Travel Agency - CompletableFuture
- 40:59Travel Agency - Stuctured Concurrency
- 44:39Welcome to ScopedValue!
- 49:40Valhalla: Value Classes
- 52:46Valhalla: Primitive Type
related talks
47mJava Next - From Amber to Loom, from Panama to Valhalla
42mJava, Today and Tomorrow
46mJava Next - From Amber to Loom, from Panama to Valhalla
51mJava Next - From Amber to Loom, from Panama to Valhalla
45mJava Next - from Amber to Loom, from Panama to Valhalla
57mJava Next - From Amber to Valhalla, from Loom to Leyden, from Babylon to Panama
50mJava Next - From Amber to Loom, from Panama to Valhalla
43mHow Amber is Driving Java’s Evolution