Ask the Java Architects

on YouTube ↗53m

" summary

Answers focus on concrete tradeoffs and designs not slogans For reconstruction the claim is that deconstructibility on classes can let wither style reconstruction work when a class supplies a canonical deconstructor and matching constructor and only for immutable semantics For named optional parameters the blockers are parameter name stability and overload resolution plus binary compatibility The history of -parameters explains why names are unreliable Collection literals are explored as a path away from arrays and the twoList vs twoSet choice illustrates API surface tradeoffs

AI-written summary · about

" chapters (15)

1. 0:00Introduction
2. 0:54Introducing Java Architects
3. 1:14Withers on mutable objects
4. 4:49Named optional parameters
5. 10:10Parameter names default
6. 15:22Project Valhalla mistakes
7. 17:53Bytecode constructor translation
8. 21:55Java complexity concerns
9. 24:06Idiomatic Java future
10. 28:11Teaching Java without arrays
11. 32:47Stream.toList vs toSet
12. 38:29Java growth and Pearl's tale
13. 44:1010 years of modules
14. 48:42Reserved keywords const goto
15. 52:25Closing remarks Q&A

" related talks

• 51mAsk the ArchitectBrian Goetz, Mark Reinhold · Jfokus 2025
• 59mMove Deliberately and Don’t Break Anything: Lessons from...JavaBrian Goetz · Philly ETE 2016
• 48mModern Java - Ask Me AnythingAna-Maria Mihalceanu, Nicolai Parlog · JCON EUROPE 2025
• 27mModern Java API DesignJonathan Giles · Jfokus 2021
• 46mCarrier Classes & Discussing SyntaxBrian Goetz, Nicolai Parlog · JavaOne 2026
• 19mAsk the Java ArchitectsBrian Goetz · Jfokus 2016
• 50mAsk the Java ArchitectBrian Goetz, Stuart Marks · Devoxx Belgium 2019
• 02h 27mEscape from the Planet of the CollectionsMaurice Naftalin, Stuart Marks · Devoxx Belgium 2024