107 points | by energeticbark 3 hours ago
5 comments
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.
It's two jits in total.
This is an incredible project for an undergraduate. Very impressive. Interesting to note that Firefox is 25% slower than Chrome/Safari, I wonder why.
Very interesting article. Would've been fun to see the comparison between native interpreter & JIT-on-WASM on iOS as well
So it's a JIT-in-JIT? JiJIT?
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
Here's a nickel kid. Go buy yourself a real computer.
Good thing I'm not running games on my 4gb Pentium 4 then.
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.
It's two jits in total.
This is an incredible project for an undergraduate. Very impressive. Interesting to note that Firefox is 25% slower than Chrome/Safari, I wonder why.
Very interesting article. Would've been fun to see the comparison between native interpreter & JIT-on-WASM on iOS as well
So it's a JIT-in-JIT? JiJIT?
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
Here's a nickel kid. Go buy yourself a real computer.
Good thing I'm not running games on my 4gb Pentium 4 then.