Java 27 and the LTS question
Six-month releases, an LTS every two years, and a decision most teams make by default rather than deliberately.
tech, developers, and the code underneath
23 pieces tagged languages,
from January 9, 2025 to September 8, 2026.
Six-month releases, an LTS every two years, and a decision most teams make by default rather than deliberately.
A release every six weeks, no exceptions, no marketing cycle. What that cadence actually produces.
Go ships every February and August, has done for a decade, and the predictability is worth more than any feature in it.
New OS versions, more on-device model surface, and a developer relationship that remains complicated.
The GIL-free build is officially supported and the ecosystem work is the actual story. A progress report.
Java, Python, C#, and JavaScript are all converging on the same feature from ML languages, thirty years late.
Every type system decision is a trade between what you can prove and what you can express. Here's how to think about where to sit.
A language that ships small releases, breaks nothing, and refuses features. Its detractors and its users are describing the same thing.
Java's concurrency change looked incremental and turned out to reshape how services get written. A field report.
Six-week releases, no breakage, and a backlog that is finally shorter than it was. What's left is the hard part.
The year in one page: what happened, what mattered, and the three things that will still matter in 2030.
More const, more stable APIs, and a language whose release notes have become pleasantly dull.