LEMON BLOG

Microcontroller development has traditionally been quite different from modern application development. In many embedded projects, the operating system, firmware, drivers, and application logic are tightly bundled together. If the app needs to change, the firmware often needs to be rebuilt, reflashed, and redeployed.

There are some projects that sound simple at first, but quickly remind you that browser-based gaming is not always as straightforward as loading a file and pressing play. Recently, I tested Final Fantasy X using the Play! PS2 emulator inside a web browser, with the intention of making the game accessible through a web-based setup. On paper, the idea was exciting. Load the emulator, fetch the ISO automatically, show a proper loading screen, and let the game run without requiring users to manually upload the game file.

Kubernetes has always been powerful, but it's never been "simple." Even something as routine as extending tooling can turn into a small project: build the plugin, package it, ship it, worry about OS differences, CPU architecture, and how safely it runs in production.

I've learned something the hard way recently — caching can be both your best friend and your worst nightmare. One day, everything on my website was lightning-fast. The next day, every single js-dos game just… died. No warning, no clues — just a cryptic WebAssembly error that sent me down the rabbit hole.