State of the Art of Java in 2026

In this GOTO State of the Art episode, Java Champion and Red Hat Senior Principal Software Engineer Ben Evans delivers a sweeping, data-driven audit of Java's health in 2026 — and the picture is far healthier than the tech press would have you believe. Server-side Java workloads have roughly doubled in the last seven years, developer wages are stable (unlike JavaScript, which is heading south), Java has been in the top four programming languages for twelve consecutive years, and the entire cloud-native infrastructure stack — Kafka, Cassandra, Spark, OpenTelemetry, Keycloak — runs on it. The real insight is mathematical: explosive growth of a small language base is still dwarfed by modest growth of Java's enormous installed base. Java isn't dying; it's just not shiny enough to get clicks.

The meat of the talk is a masterclass in Java's architecture and roadmap. Ben unpacks the fundamental tension between dynamism (the JVM's Lisp-and-Smalltalk-heritage runtime) and integrity (modern security demands that restrict unchecked internal API access), before walking through the near and far future: Project Valhalla's value types (the most fundamental change to Java ever — bigger than generics or lambdas), the Vector API waiting on Valhalla to land, nullability markers, ahead-of-time compilation, and beyond that, type classes and Project Babylon.

His honest take on AI tooling is sharp: great for greenfield, genuinely poor at architectural reasoning and version-specific code, and only a real productivity multiplier for teams who already have solid engineering practices. Oh, and it's a wolf in sheep's clothing — the JVM's dynamism makes it way closer to Lisp than to C++, and Java's philosophy of "boring done right" turns out to be an excellent foundation for AI-era enterprise software.