Chrome OS proved the concept a decade ago - that most people didn’t need a traditional operating system, they needed a browser with decent hardware underneath it. The tech press largely treated this as a niche play for schools and budget shoppers. It wasn’t. It was a preview.
The shift that’s happened since is less dramatic but more total. On Windows and macOS, the browser has become the primary runtime for an increasing share of professional work. Figma, Linear, Notion, Google Docs, VS Code in its web form - these aren’t thin clients filling a gap left by missing native software. They are, in most practical respects, better than the native alternatives they replaced. Figma outcompeted Sketch on features while living entirely in a tab. That isn’t a coincidence of timing; it’s a structural advantage. Web apps update silently, sync state across devices without configuration, and require no install gate between a new user and the product.
Why Windows and macOS Still Exist
The honest answer is: graphics, audio production, and inertia - roughly in that order. Final Cut Pro, Ableton Live, and professional GPU workloads are not moving to the browser anytime soon. Neither is anything that requires deep system access or low-latency hardware calls. But this is a shrinking share of what most knowledge workers actually do in a given day. Email, documents, project management, communication, code review - all of it now runs comfortably in Chrome or Safari with no meaningful compromise.
Microsoft’s own response to this has been telling. The company has spent years pushing progressive web app support in Edge and allowing PWAs to be installed as quasi-native apps. They’re not fighting the browser’s ascendance. They’re trying to stay relevant inside it.
The Part That Gets Overlooked
Security posture has shifted quietly alongside this. Browser sandboxing has become the default containment model for most user-facing software, which is almost certainly a net improvement over the era of native apps with promiscuous system access.
What’s less clear is what this means for operating system development as a creative or competitive space. If the browser is where users live, the OS increasingly becomes infrastructure - something you tune and patch rather than something you design around. Apple is the one major player still resisting this framing, betting that tight hardware-software integration justifies keeping users native. Whether that bet holds in another ten years is genuinely uncertain.