Module Adoption? JDK Build Tool? Lombok? Backwards Compatibility? - Ask the Architects
summary
Structured concurrency is effectively production ready and sits in a seventh preview while Project Babylon already has a JEP submitted and targets GPU offload and automatic differentiation tests. Module adoption stalls because build tools and library re‑architecture cost outweigh immediate benefits. Streams are a known loop customization challenge where Babylon or fusion could give hot pipelines native speed. Lombok is criticized for compiler hacks and for propping up old Java bean idioms. AI helps spec and test updates but requires human oversight.
AI-written summary · about
chapters (15)
- 0:00intro
- 2:18State of Structured Concurrency
- 4:35State of Project Babylon
- 6:34Feature Prioritization
- 12:56Module Adoption
- 19:38Stream API Performance Improvements
- 29:49Module vs Class Path
- 33:42Thoughts on Lombok
- 36:42Object Header Size
- 37:16Thoughts on a JDK Build Tool
- 39:38"What Are Your Pet Projects?"
- 45:44Use of AI Tooling in JDK Development
- 53:06Advanced Hardware Information and Interaction
- 54:36Breaking Backwards Compatibility
- 55:52Next Generation of Java Developers
related talks
52mValhalla? Python? Withers? Lombok? - Ask the Architects
45mBeyond the Hype: Unpacking the Latest Features of JDK
50mAsk the Java Architect
51mAsk the Architect
48mModern Java - Ask Me Anything
52mAsk the JDK Architects
57mJava Next - From Amber to Valhalla, from Loom to Leyden, from Babylon to Panama
53mHacking Java