Abstractions are wonderful until they become the bottleneck.

Kurogane started as a GPU-heavy FPS prototype built with Tauri. It flew on Windows (WebView2) out-of-the-box but on Linux I kept running into compositor quirks, inconsistent GPU behavior and a frustrating lack of control over the rendering pipeline.

I wasn't trying to build another desktop framework. I was trying to understand why the exact same application behaved like two different programs depending on the operating system it ran on.

Following that trail led me beneath Tauri and system WebViews into Chromium itself. Kurogane gradually became a way to understand where abstractions begin to leak, what desktop frameworks intentionally hide and how much of Chromium could be exposed without exposing all of its complexity.

Kurogane also became my excuse to learn Rust “properly”. Chromium, on the other hand, let's just say was less welcoming. Years of historical APIs and documentation has a personality of its own.

I set out to explain a rendering anomaly. I ended up with a Chromium runtime, a much deeper appreciation for modern browser architecture and a healthy respect for just how many layers modern desktop applications stand on.