How the industry moves on from Java 8?
summary
Industry telemetry shows 75% on Java 8 and New Relic data hints at >80% across flavors, so adoption lags despite JDK 9–15 features. Migration pain points are concrete: missing JAXB, module warnings, library and app‑server incompatibilities, subtle runtime regressions and vendor/licensing concerns. Spring and many big libs already run on JDK 15, AdoptOpenJDK/Adoptium builds are viable, and the practical path is JDK 8 → JDK 11 migration supported by tooling, bug reporting and a centralized migration guide / knowledge base.
AI-written summary · about
chapters (4)
- 0:00Start
- 3:09Java Eight Is out of Support
- 32:47How Do I Convince My Management That I Need To Move
- 1:01:15What Do We Need To Do To Make Java More Compelling
related talks
50mJava 9/10/11 - What's new and why you should upgrade
49mJDK 8 to 25 Without the Pain - Engineering a Modern Java Platform
46mBeam Me Up, Java! A Journey through Java LTS Versions 11 to 21
43mEngineering a Modern Java Platform
49mJDK LTS Release Use Cases: When is a Java migration advisable?
53mApproaching the JDK 25 LTS release through real-world migration
41mModern Java for the Masses! Is Java Still Relevant
46mGoing Java::Current in Production