Of course it beats a native interpreter. WASM overhead is about 20%, interpreter overhead is about 1000%.
replyWhat's cool here is to have a GameBoy JIT runtime at all.
It's two jits in total.
replyThis is an incredible project for an undergraduate. Very impressive.
Interesting to note that Firefox is 25% slower than Chrome/Safari, I wonder why.
reply[flagged]
replyWhat 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.
replyI'd hire an undergraduate who can produce this level of work with Claude.
replyEvery 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.
replyFor the times they are a-changin'
So it's a JIT-in-JIT? JiJIT?
replyVery interesting article. Would've been fun to see the comparison between native interpreter & JIT-on-WASM on iOS as well
reply[dead]
replyyet 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
replyHere's a nickel kid. Go buy yourself a real computer.
replyGood thing I'm not running games on my 4gb Pentium 4 then.
reply