WATaBoy: JIT-Ing Game Boy Instructions to WASM Beats a Native Interpreter
95 points by energeticbark 3 hours ago | 10 comments

jonny_eh 3 minutes ago
So it's a JIT-in-JIT? JiJIT?
reply
ahartmetz 40 minutes ago
Of course it beats a native interpreter. WASM overhead is about 20%, interpreter overhead is about 1000%.

What's cool here is to have a GameBoy JIT runtime at all.

reply
grashalm 10 minutes ago
It's two jits in total.
reply
dag100 2 hours ago
This is an incredible project for an undergraduate. Very impressive. Interesting to note that Firefox is 25% slower than Chrome/Safari, I wonder why.
reply
tmpz22 2 hours ago
[flagged]
reply
koolala 2 hours ago
What are you basing this statement on? The code comments read very human to me. Your the one hurting their chances of finding a job by falsely saying this.
reply
simonw 60 minutes ago
I'd hire an undergraduate who can produce this level of work with Claude.
reply
godwinson__4-8 2 hours ago
Every company they apply to will be leveraging LLMs. Time to get over it. No need to be grumpy old man about such things. Every generation has faced such foes. The old always yields to the new.

For the times they are a-changin'

reply
milch 2 hours ago
Very interesting article. Would've been fun to see the comparison between native interpreter & JIT-on-WASM on iOS as well
reply
bebenebenebeb 3 hours ago
[dead]
reply
iberator 2 hours ago
yet on real old hardware it would be 20x slower in real life. same as all native javascript junk - its fast, but non usuable on older hardware
reply
switchbak 2 hours ago
Good thing I'm not running games on my 4gb Pentium 4 then.
reply