From Cowboy Mode to Careful Stewardship
summary
Java’s roadmap shifts from rapid feature churn to integrity by default: modules land in JDK 9, strong encapsulation turns on by default in 16 and is enforced in 17, letting maintainers refactor and remove legacy bits (Java EE modules dropped). Removing private static fields once breaks every app server because an Apache XML library used reflection. Critical internals like sun.misc.Unsafe stay but get standard replacements (VarHandles, Panama) and a gradual deprecation plan; an analysis finds 3 of 6 recent JDK zero‑days would be blocked by encapsulation.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:53Java's Early Days
- 4:40A History of Breaking Changes
- 9:16sun.misc.Unsafe
- 12:58OpenJDK vs Hyrum's Law
- 16:06Enabling Evolution Through Encapsulation
- 20:42Deliberate Evolution
- 26:22Benefits of Integrity
- 30:21Final Should Mean Final
- 33:20Troublesome Features Aren't (Automatically) Bad
- 34:22There's no Module *System*
- 39:09The Journey Towards Integrity
