6 posts tagged with "performance"

The Chrome team shipped Modern Web Guidance 1.0 on November 10, 2026, and a day later published the top 10 things AI gets wrong in web development. We first mentioned the project in our Google I/O recap when it was an early preview. With the stable release, it is worth a closer look.

This post covers what Modern Web Guidance (MWG) is, how it works, what it fixes, and how it fits our recommended tech stack. Short version: the guidance is good and mostly matches what we want. But two parts need care: our component libraries already handle some of the things MWG wants to rewrite, and the default install command breaks our supply-chain rules.

"Rewrite it in X, agents are better at X" has become a common argument in frontend teams, and it almost never comes with numbers. Nolan Lawson's The AI cost of JavaScript frameworks (October 28, 2026) is one of the first attempts to measure it. He had the same coding agent build the same app in 12 frameworks, five times each, and tracked what it cost, how long it took, how much code it produced, and how fast the result loaded. This post summarizes the findings, the caveats that matter, and what they mean for the Aliz tech stack.

TypeScript 7.1 Beta landed on October 20, 2026. When TypeScript 7.0 shipped in July, the Go-based compiler was fast but had one big gap: there was no programmatic API. 7.1 closes it. It brings a new, stable-track compiler API, a plugin point called content mappers for non-TypeScript files like .vue components, and another big round of performance work. It also adds a few language and lib features. This post covers what changed, what it unblocks, and whether you should try the beta now.

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.