3 posts tagged with "performance"

The DuckDB-WASM + OPFS announcement on September 18, by Carlo Piovesan and Geertjan Wielenga, is the kind of headline that reads like a novelty — an analytical database engine, compiled to WebAssembly, persisting to a real file system inside a browser tab. But the novelty isn't DuckDB. It's the platform layer underneath it. Over the last few years the Origin Private File System (OPFS) quietly turned the browser into a place you can run a real database, not just a cache with delusions of grandeur. The interesting question isn't "can DuckDB do this?" — plenty of engines can now. It's what changed at the platform layer to make any of them possible, and whether your project should care.

React 19.3 shipped on September 9, 2026. Two APIs that have been sitting in the experimental drawer since the April 2025 React Labs post — <ViewTransition> and Fragment Refs — are now stable, joined by a browser() escape hatch for SSR, Trusted Types passthrough, and Context rendering in Server Components. There are no breaking changes, no deprecations, no codemods, and no upgrade guide, because none are needed. The interesting question isn't whether to bump the version. It's which of these APIs earn a place in your codebase.

TypeScript 7.0 shipped on July 8, 2026. The compiler is now written in Go — a line-by-line port of the existing TypeScript codebase (codename "Corsa"), not a from-scratch rewrite. The result is 8–12x faster builds, dramatically faster editor responsiveness, and a language server that crashes far less often. This is the single biggest performance improvement in TypeScript's 12-year history. But it comes with real breaking changes, a missing programmatic API, and a migration path that rewards patience over haste.