10 Surprises for a JVM Engineer in Real Life Java Development
summary
Ten concrete takeaways: frameworks mostly stay the same and moving off Java 8 proves surprisingly hard because Spring Boot and logging break upgrades; client GUI tooling fails so a company-built bootstrapper ships runtimes and updates; garbage collection rarely causes visible pauses but heap sizing and parsing GC logs force fragile ad hoc tooling (tailing files, custom parsers, or using Java Flight Recorder); startup time and cloud resource sizing matter; database connection handling is under-optimized; streams (via JavaFX use case and back end) noticeably change code shape and readability.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:57About Me
- 3:18The Java Frameworks 1999-2006
- 4:21JVM Development
- 5:09Looklet and Java
- 7:47Surprise 12
- 7:58Still no Good GUI Framework
- 9:56Surprise 3
- 10:08Nobody Cares About GC
- 14:45Hard to Get to the GC Information
- 23:12Optimizations for DB and OR Mappings
- 29:06Legacy is Still Legacy
- 32:54Java Strategy Confusing
- 34:04Conclusion
- 34:48Wish List to the Java Platform Team
related talks
54mJava Forever (Round Table).
37mHow I learned to stop being afraid and love the JVM
51mLife Beyond Java 8
50mJava 8 to 17+ Upgrade - Lessons Learned and Best Practices
01h 01m20 Years of Java
46mGoing Java::Current in Production
41mModern Java for the Masses! Is Java Still Relevant
59mEffective Java SE 18 APIs/Lang features, makes your life easier.