Building a Browser Game with React: What Doesn’t work well (Run Away From Work)

<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>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><a href="https://7coderwords.kenamick.com/" rel="noopener noreferrer">7 CODER W🙂RDS</a> is a word puzzle game for people interested in computer science in general. You are

<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

<h2> The Challenge </h2> <p>No sprites. No assets. No external images. Just a browser, TypeScript, and the Canvas 2D API. Could I build a playable RPG?</p> <p>The answer is yes —

<p>Eight months ago I was frustrated. I do strength training, <br /> running, and BJJ — and I needed three different apps to <br /> track everything. Strava for runs, Strong for

<p>The server was running. The Rust was making sense. But on the client side, I had a problem I hadn't anticipated: React and real-time rendering don't want the same things.</p>