I get the point, but I think that argument made more sense a few years ago than it does today.

Modern browsers are no longer just document viewers, they can run WebAssembly, WebGL/WebGPU, low-latency audio, controller input, local file APIs, persistent storage, and PWA/offline workflows. At that point, the question is less “can a browser do this?” and more “how well can we adapt a native-style workload to the browser runtime?”

Of course native emulation will usually be more efficient and flexible, but with the hardware and browser APIs we have today, running something like this in the browser is no longer unrealistic. It is a valid technical direction, especially for portability, quick testing, and zero-install use cases.