Tukuk-OSThe Plugin Era Died and Nobody Mourned It
For years "web games" meant a proprietary plugin: Flash ruled the format, and when Adobe retired it in December 2020, an entire library of playroom classics vanished from the live web overnight (archives like Flashpoint rescue tens of thousands). The death of plugins was not the end of web gaming — it was the beginning. The open web had, quietly, grown a gaming stack of its own: HTML5 canvas for 2D, WebGL for hardware-accelerated 3D (a browser-standard version of the graphics APIs game engines use), and JavaScript engines fast enough to run real game loops. What used to require a runtime you downloaded and trusted blindly is now part of the platform you open for email.
WebAssembly: Console Speed in a Tab
The second shift was the one developers felt most. WebAssembly (Wasm, standardised 2017) lets code written in C++, Rust or Go compile into a near-native bytecode the browser executes at close to desktop speed, with strict sandboxing. Porting an existing game engine became an engineering task instead of a rewrite: Unity and Godot both ship browser targets, and classic engines — even DOS emulators — now run inside a tab. That is why a browser game today can have real collision physics, pathfinding and shaders: the heavy lifting is native-speed code, and the browser handles input, audio and display through standard APIs like WebAudio and requestAnimationFrame.
The Third Piece: Servers That Talk Back
Great single-player ports still could not do what consoles do — multiplayer and cloud saves — until websockets, HTTP/2 and edge servers matured enough for the browser to hold open, low-latency conversations with a backend. Real-time positions, chat and leaderboards over plain web protocols made browser games social without a client install, and progressive-web-app tech let a game you liked be "installed" as an offline-capable shortcut when you actually want one. The result is a spectrum: instant tap-to-play link, saved-to-home-screen PWA, or full store app — same engine, three levels of commitment. The arcade at tukuk.org/games runs entirely on that first tier: every title playable in the tab it opened in, with no account required to start.
What the Browser Does Not Solve
Honest limits remain, and reviewers should know them. Mobile browsers historically capped memory and throttled background tabs, so big 3D worlds still get squeezed on phones; audio latency is worse than native; and a tab has no direct access to a gamepad's full feature set or to system-level performance counters. Cloud gaming (streaming a desktop GPU's frames to any screen) attacks the first problem by moving the hardware elsewhere entirely, trading bandwidth for power. And discoverability still favours stores: a browser game competes with an algorithm, not a shelf. The web won the capability argument; the fights still being waged are over distribution and persistence.
Why It Matters Beyond Play
The browser game revolution is the clearest everyday proof that the open web closed the capability gap that plugins once owned: a world now runs standards, not installations — the same philosophy behind the no-install mini-apps collected at tukuk.org/apps and the free tools in the utilities hub at tukuk.org/alat. Next time a link opens into a playable 3D world, remember the quiet stack underneath: a dead plugin's ghost, a native-speed sandbox, and two-way servers — and the strangest fact of all, that none of it needed anyone to click "install."