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
24 pieces tagged releases,
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 new major version every autumn, a five-year support window, and a migration that gets worse the longer you leave it.
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.
The GIL-free build is officially supported and the ecosystem work is the actual story. A progress report.
Type stripping, a mature test runner, and a standard library that absorbed the ecosystem. You can ship TypeScript with no toolchain.
Six-week releases, no breakage, and a backlog that is finally shorter than it was. What's left is the hard part.
More const, more stable APIs, and a language whose release notes have become pleasantly dull.
More const, more stable APIs, and an ecosystem that keeps finding ways to need less unsafe code.
Long-term support for the batteries-included Node, plus a look at where Deno and Bun actually landed.
The GIL-free build graduates from experimental, template strings land, and annotations finally get lazy evaluation.
Inferred array lengths in const generic position, plus x86 SIMD stabilizations that matter for anyone doing math.