The OS Used to Mean Something

For most of the 2000s, your operating system was the product. You bought Windows XP, you bought Vista (or tried not to), you upgraded to 7 and felt the relief of a well-made thing. The browser was a tool you launched from the OS. Now that relationship has quietly inverted.

Chrome’s market share across desktop browsers sits north of 65% by most tracking estimates, and that number undersells its actual reach - Chromium, the open-source base Chrome is built on, also powers Edge, Brave, Opera, and Vivaldi. The browser monoculture is already here. The browser platform monoculture is what’s coming next.

What “Platform” Actually Means Now

Progressive Web Apps were supposed to be a niche workaround for mobile web developers who couldn’t stomach the App Store’s cut. They’ve become something more structurally significant. Figma ran in a browser before Adobe bought it. Notion, Linear, Cron - tools that serious professionals use all day - work identically in Chrome on Windows, macOS, or ChromeOS. The operating system underneath has become largely irrelevant to the experience.

This is, deliberately or not, exactly what Google has been building toward since Chrome OS launched in 2011. The pitch back then was mocked as impractical: what if your computer was just a browser? The joke’s on everyone who laughed. The difference now is that it’s not ChromeOS doing it - it’s Chrome itself, running on every OS, turning them all into equivalent substrates.

Microsoft has noticed. The aggressive push to make Edge the default browser in Windows 11, complete with repeated prompts and friction when you try to switch, isn’t just about ad revenue. It’s about not ceding the entire application layer of Windows to a Google product.

This Isn’t a Firefox Problem

Firefox’s decline is often framed as a tragedy of UX or marketing. That’s not quite right. Firefox lost because it wasn’t backed by a platform with financial incentives to bundle it everywhere, and because the sites that set the baseline - Google’s own properties, especially - were quietly tuned to perform best on Chrome. Mozilla can’t compete with that. No independent browser can, structurally.

What’s less clear is what this convergence means for computing five years out. If the browser is the OS, then whoever controls the browser’s extension ecosystem, its Web APIs, and its performance decisions controls what software you can run - and right now that’s effectively one company, with all the accountability problems that implies.