Ask the Architect
summary
Panel answers why the security manager removed from the JDK: running untrusted code migrates to OS containers and external tooling, not the JVM, and replacement work lives in OpenJDK discussions and JBS issues. String templates withdrawn from JDK 23 after prototype examples proved the processor API couldn’t express needed code. Vector API stays in preview pending JEP 401 (Valhalla). IO_uring prototypes show bookkeeping costs outweigh benefits; Panama FFM (foreign-memory/function) is the practical interop path today.
AI-written summary · about
chapters (17)
- 0:00Introduction and setup
- 2:29Security manager deprecation
- 6:00Tip and tail JEP explained
- 8:10String templates removal
- 11:05Vector API status update
- 13:11Deprecating obsolete classes
- 16:06IO_uring and platform specifics
- 21:46Exception stack trace truncation
- 23:53Tail call elimination status
- 26:22Project readiness and done
- 30:21Java upgrade value proposition
- 34:35Max function type bounds
- 36:41Java's future and competitors
- 43:25Distant horizon features
- 45:52Large collection sizes
- 51:50JavaDoc improvements
- 54:17Call to action and closing
related talks
52mAsk the JDK Architects
48mModern Java - Ask Me Anything
49mJPoint 2023 TechRadar: Java Virtual Machine
51mAsk the Architect
57mJava Next - From Amber to Valhalla, from Loom to Leyden, from Babylon to Panama
50mJava Next - From Amber to Loom, from Panama to Valhalla
45mBeyond the Hype: Unpacking the Latest Features of JDK
22mDeprecations and Removals