Language Specification Class file Runtime Tooling

Java evolution is easiest to understand when all layers stay in view together.

This vertical ties together release history across source language changes, the formal specs, bytecode format, runtime execution, packaging, and tools. It acts as the bridge page between the individual deep-dive sections. It also helps keep the visible future LTS line in view so the whole system can be planned as an evolving stack.

Read evolution across layers

Java Language shows what developers could express at each release.
JLS captures how those rules were formalized.
JVM & Class File tracks compiled compatibility and runtime contracts.
JDK & Tools shows how platform capabilities and workflows matured.

Where to go next

Java LanguageUse the release-by-release Java vertical as the main historical path. JLSOpen the language-spec vertical when the question is about formal rules or semantics. JVM & Class FileFollow binary format and compatibility evolution. JDK & ToolsSee how runtime packaging, diagnostics, and developer tooling changed.

Visible future LTS line across the stack

The next decade is already visible enough to discuss as a planning horizon: Java 29, 33, 37, and 41 form the projected LTS rhythm, and that rhythm affects the Java language, JLS, class file versions, JDK packaging/tooling, framework baselines, and migration strategy together.

Planning view: Java 29 (Sep 2027), Java 33 (Sep 2029), Java 37 (Sep 2031), Java 41 (Sep 2033).

Existing deeper page

The older evolution page is still available as an additional reading surface. This common landing page is now the main header destination so the top navigation stays consistent with the other verticals.

Open legacy evolution page