The Browser Was the Engine

<p>I built an open-source browser precision game called <strong>Path Protocol</strong> — 100 levels, a Theme Workshop for authoring your own courses, MIT licensed. Along the way,

<p>Cave Story should not have survived. A solo developer with no engine, no map editor, and no budget spent five years building a 15-level Metroidvania in his free time — and

<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>Hey everyone! I've always been a fan of retro gaming, and I recently decided to take on the challenge of porting the original 1993 DOOM to the browser. </p> <p>The result is

<p><em>Cover: AI-generated concept illustration of a hypothetical foldable phone, not a photograph of existing hardware or a screenshot of the emulator.</em></p> <p>It started

<p><a class="article-body-image-wrapper"

<p>Chrome wasn't "crashing."</p> <p>It was just...slowly suffocating my system.</p> <p>Over time, RAM usage would creep up. Background tabs accumulated state. Other applications

<p>Every time I debugged a deeply nested API response, I scrolled. I counted brackets. I lost my place. After the third or fourth time of doing this for the same Stripe webhook, I