Every streaming team has a state budget, and joins eat most of it.
Every Vite project that shipped in 2025 ran on two separate bundlers.
Every project I've touched in the last five years has a file somewhere — maybe lazyVideo.js, maybe useMediaObserver.
Every SvelteKit app I built before version 2.39 had the same awkward middle layer: a +server.
Last week I added a fifth MCP server to a coding agent I've been running in production. Response quality dropped off a cliff.
Vite 8 landed on March 12 with exactly one headline change: Rolldown replaced both esbuild and Rollup as the bundler. Two dependencies out, one Rust binary in.
The React Compiler hit v1.0 in October 2025.
TypeScript 7.0 beta dropped on April 21.
Back in 2019, Chrome 76 shipped loading="lazy" for images, and the web performance crowd collectively exhaled.
There's a V8 implementation detail that most JavaScript developers never think about: every time a JSON.
Every major framework is in the same race right now: ditch the virtual DOM, or at least make it optional. Svelte got there first by never having one.
Vite had a dirty secret for its entire existence: it used two different bundlers. esbuild for dev, Rollup for production.
PostgreSQL 18 shipped last September and it's already past its first point release.
Framework releases are supposed to make your life easier. Next.
TypeScript 6.0 shipped on March 17 to the usual fanfare — Temporal types, better method inference, subpath imports.
The virtual DOM was supposed to be Vue's selling point.
I've written the same IntersectionObserver wrapper for deferring offscreen video loads on at least four different projects.
Every Vite project before version 8 ran two bundlers behind the scenes. esbuild handled dev, Rollup handled prod.
Zone.js was Angular's original sin.