No QA: Modern Java: Change is the Only Constant
summary
Platform is split into 26 standard modules (later trimmed to 19), old internals are being strongly encapsulated with tooling like jdeps/javac warnings and jlink-style custom runtimes, and components such as Java EE and CORBA are removed. Release cadence moves to a strict six-month rhythm (JDK 9→13) with feature counts: 90 JEPs in JDK 9, 12 in JDK 10, 17 in JDK 11, 8 in JDK 12, ~2,500 JDK 11 bugs fixed; modularization reduces image sizes and prevents roughly three of six high-impact zero-days.
AI-written summary · about
chapters (17)
- 0:00Modern Java changes
- 1:25Java modernization need
- 2:30Modularizing Java platform
- 4:19Modular JDK benefits
- 6:28Internal API deprecation
- 8:59Modularization compatibility
- 9:39Legacy components removal
- 12:26Six-month release cadence
- 13:51JDK feature contributions
- 16:19Non-LTS releases
- 17:01LTS update strategy
- 19:26LTS future and community
- 21:59LTS vs feature releases
- 23:44Java changes concerns
- 24:30Ecosystem readiness
- 25:33Upgrade dependencies now
- 25:53Java features roadmap
related talks
27mModern Java: Change is the Only Constant
50mKeeping up with Java: Look at All These New Features!
56mJDK 9 & 10: Mission Accomplished, What Next For Java
46mKeeping Up with Java
45mThe Future of Java is now!
46mJDK 9, 10 and 11: Pitfalls For The Unwary
55mRapid Java Innovation
51mMoving Java Forward Faster