The most consequential performance story of the last decade is one almost nobody wrote up: the browser quietly became a legitimate game runtime, and most developers' priors never updated.
The priors were earned. Browser gaming's first era ran on plugins and interpreted JavaScript: indirect rendering, unpredictable GC pauses, audio APIs that fought you. "Laggy web game" wasn't prejudice; it was measurement.
Then the measurements changed, component by component.
Rendering: WebGL gave pages a direct path to the GPU, and its successors have pushed that access lower still. Canvas stopped being the bottleneck; scenes that once slideshow'd now hold frame rate on integrated graphics.
Compute: JIT-compiled JavaScript got fast enough for most game logic years ago, and WebAssembly ended the argument for the rest — near-native execution for the hot paths, and a compile target that let entire native engines ship to the web.
The rest of the stack came along: real-time audio graphs, gamepad input, pointer lock, fullscreen — each a small standard, together a console-shaped API surface.
Hardware moved too. A mid-range phone from a few years back — the device your actual audience owns — runs a competent HTML5 game at full frame rate in a tab, with thermal headroom to spare. The floor rose under everyone.
What makes this professionally interesting is the asymmetry it created. Technical capability arrived; commercial infrastructure didn't. A store game gets a storefront, rankings, a discovery pipeline. A browser game gets a URL. Capability without findability produced today's odd landscape: a format that outperforms its reputation, full of good games no stranger has ever seen, built by developers who blame themselves for it.
That missing layer is the one my team operates — Malaguo; disclosure, this is where the pitch lives. We publish HTML5 games: you upload a ZIP with index.html at the root. Security is not vibes — the archive is quarantined before anything executes, structure and dependencies and runtime behavior get inspected, automated playability checks run, and a human plays the exact submitted version before anything gets a public URL. Approval triggers the commercial layer the format never had: per-game pages, whole-page translation into multiple languages, per-language search indexing, global CDN distribution, ad integration on the game's own pages, and payouts, with the bigger share going to the creator. No listing fee. No exclusivity — ship the same build everywhere else you like. Terms readable before signup.
If you benchmarked the browser years ago and filed it under "toys," rerun the benchmark. The runtime kept its side of the bargain. The missing half was never the tech — and the missing half is now on offer.
Top comments (0)