Top
Best
New

Posted by energeticbark 3 hours ago

WATaBoy: JIT-Ing Game Boy Instructions to WASM Beats a Native Interpreter(humphri.es)
98 points | 11 comments
ahartmetz 53 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.

grashalm 24 minutes ago|
It's two jits in total.
dag100 1 hour 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.
tmpz22 1 hour ago|
[flagged]
koolala 1 hour 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.
simonw 1 hour ago||||
I'd hire an undergraduate who can produce this level of work with Claude.
godwinson__4-8 1 hour 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'

jonny_eh 17 minutes ago||
So it's a JIT-in-JIT? JiJIT?
milch 1 hour ago||
Very interesting article. Would've been fun to see the comparison between native interpreter & JIT-on-WASM on iOS as well
bebenebenebeb 2 hours ago||
[dead]
iberator 1 hour 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
qweqwe14 10 minutes ago||
Here's a nickel kid. Go buy yourself a real computer.
switchbak 1 hour ago||
Good thing I'm not running games on my 4gb Pentium 4 then.