An undergrad's Game Boy emulator beats a native interpreter by JIT-ing to WebAssembly (humphri.es)
The trick is the second layer. WATaBoy emits WebAssembly bytecode for hot game code, and Safari's engine compiles that Wasm to native machine code on its own — so the emulator rides the browser's JIT instead of fighting it.
A systems engineer in the thread deflated the surprise with arithmetic: Wasm overhead runs near 20 percent, an interpreter's loop overhead near 1000. Beating the interpreter was never the hard part. The novelty is a Game Boy JIT runtime existing at all.
Sign in to save