part2 – Ted Neward
summary
Academia births languages that promise lightweight fibers with no shared mutable state but fail on real production needs: no DB bindings, weak XML tooling, immature garbage collectors that pause under load. The JVM wins because of decades of engineering—HotSpot descended from Strongtalk work and roughly 20–30 engineers iterating for years—so Java solves scale and GC pain. Rapid user feedback beats long academic cycles; prototypes get shelved when they don't reach practical integration points.
AI-written summary · about
related talks
35mJava at Speed: Building a Better JVM
01h 01mJava compilers: Why Java is one of the first options for Low latency apps
01h 00mon Java - Historical Oddities & Persistent Itches
45mJava Innovations - from Developer-driven features to (...)
44mJava at Speed: Building a Better JVM.
01h 10mJames Gosling Q&A session
59mKeynote: Industry GC Insights from OpenJDK
54mJava Forever (Round Table).