Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

100% Positive

Analyzed from 79 words in the discussion.

Trending Topics

#native#interpreter#wasm#overhead#jit#interesting#slower#real#hardware#course

Discussion (8 Comments)Read Original on HackerNews

ahartmetz30 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.

dag100about 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.
milchabout 2 hours ago
Very interesting article. Would've been fun to see the comparison between native interpreter & JIT-on-WASM on iOS as well
iberatorabout 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
switchbakabout 1 hour ago
Good thing I'm not running games on my 4gb Pentium 4 then.