Why Agar.io and Slither.io Bet on Node.js, WebSockets, and Canvas: The Boring Web Stack Behind the .io Boom
The .io boom looks like a design story. It was really a server-bill story. Agar.io was built by 19-year-old Brazilian developer Matheus Valadares and released on agar.io on 28 April 2015 after a single 4chan /v/ playtest post. It was written in JavaScript and C++, published on mobile by Miniclip in July 2015, and became one of the most popular browser and mobile games of its first year largely…
The .io game genre, consisting of browser-based multiplayer arena games, emerged due to a deliberate choice of a "boring" web stack: JavaScript on the client, HTML5 Canvas for 2D rendering, Node.js on the server, and WebSockets (via Socket.IO) for real-time bi-directional traffic. This stack allowed developers to create simple yet addictive games that could run smoothly on limited bandwidth and retain players through quick, iterative gameplay.
The simplicity of the games reduced the demand for resources, making them ideal for widespread adoption during the COVID-19 pandemic. Node.js, in particular, provided an efficient platform for handling numerous connections concurrently without requiring the overhead of thread-per-connection, making it an ideal choice for solo developers looking to create low-cost, scalable network applications.
By focusing on server moves and client rendering, these games achieved a unique balance of simplicity and engaging gameplay, while also providing a seamless player experience even in situations with varying network conditions.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
