Ask the Architect
summary
Live AMA covers concrete roadmaps: a serialization prototype using pattern matching that asks class authors to supply at-rest constructors and deconstructors, migration paths for old Java IO serialization, and a plan to deprecate unsafe APIs while replacing them with the foreign-memory API (Java 23) and other platform features. JEPs evolve openly (JEP 401 for Valhalla took many revisions), corpus scans over Maven Central guide removals, and records intentionally avoid per-component default values to preserve refactorability.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:11Java null pointers future
- 5:05JEPs shape Java platform
- 9:26Java serialization future
- 13:21Why remove serialization hard
- 19:28Project Valhalla impact
- 24:31Stream API limits improvements
- 26:24Records constructors defaults
- 32:12Java reserved 'const' mystery
- 33:18Java deprecation policies
- 41:28Lombok Java tooling need
- 44:08Removing Unsafe API integrity
- 47:53Java concurrency book updates
- 49:03Toxic Java features trade-offs
- 50:27Closing remarks hiring
related talks
48mModern Java - Ask Me Anything
50mAsk the Java Architect
46mWhere is the Java language going?
52mAsk the JDK Architects
55mAsk the Architect
58mModule Adoption? JDK Build Tool? Lombok? Backwards Compatibility? - Ask the Architects
47mJava Next - From Amber to Loom, from Panama to Valhalla
21mAmber & Valhalla - Incremental Design and Feature Arcs