building an atomic bomberman clone, part 4: react vs. the game loop

<p><em>A free game center at <a href="https://wqnlll.github.io" rel="noopener noreferrer">wqnlll.github.io</a> — no framework, no build step, no npm install. Just HTML files on

<p>In the late 90s, my brother, my cousin, and I would crowd around a single PC and play Atomic Bomberman for hours. Arrow keys and WASD, elbows bumping, trash talk flying. It was

<p><em>Posted by Prateek | March 2026</em></p> <p>I shipped React 19 in production when it was still RC. Not because I love living dangerously — well, maybe a little — but because

<p>Hi!</p> <p>I'm <a href="https://github.com/nyaomaru" rel="noopener noreferrer">@nyaomaru</a>, a frontend engineer who finally managed to make it to the first zombie in

<p>Modern frontend development has normalized an absurd amount of complexity.</p> <p>Want to build a real-time app or simulation game?</p> <p>Apparently you now need:</p> <ul>

<p>I build TagKing.io on my own: a two player game of tag that runs in a browser tab. One player is "it", touching the other passes it on, and whoever is "it" when thirty seconds

<p>Two new games live at <a href="https://play.pickuma.com" rel="noopener noreferrer">play.pickuma.com</a>: a single-button time-sense test called <strong><a

<p><em>Part I of the series "Don't Let the User Wait - Render Quickly to Keep Their Attention."</em></p> <h2> The problem hiding inside SSR </h2> <p>Server-Side Rendering promises