Postcards from the Peak of Complexity
summary
Java evolves through decade-scale projects — generics, lambdas, modules, Loom (virtual threads) and Valhalla — and follows a repeatable life cycle: early optimism, a harsh trough, a working-but-overengineered peak of complexity, then painstaking simplification toward a virtuous collapse. Serialization is the cautionary failure that costs decades of patches; Loom shows a concrete design choice (fusing fibers into threads) that improves interoperability; Valhalla recently achieves simplification after many iterations. Expect concrete war stories, timelines measured in years not weeks, and specific design tradeoffs and failures.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:35The way we work
- 2:50Why do things take a long time
- 5:18Why do we do it
- 6:24The design process
- 8:41The Gartner Hype Cycle
- 9:17The Five Stages of Grief
- 11:19TheVirtuous Collapse
- 12:26The Most Dangerous Moment
- 13:57Serialization
- 15:40Reaching the Peak
- 17:01Falling in Love with Complexity
- 19:57Getting rid of things
- 21:19Slow over time
- 21:48Closing thoughts
- 22:50Java Platform Group
related talks
50mJava Next - From Amber to Loom, from Panama to Valhalla
46mJava Next - From Amber to Loom, from Panama to Valhalla
41mThis Ain’t Your Parents’ Java
45mJava Next - from Amber to Loom, from Panama to Valhalla
52mValhalla? Python? Withers? Lombok? - Ask the Architects
59mMove Deliberately and Don’t Break Anything: Lessons from...Java
45mBeyond the Hype: Unpacking the Latest Features of JDK
47mJava Next - From Amber to Loom, from Panama to Valhalla