Live data from Hacker News

JavaScript engines zoo – Compare every JavaScript engine

zoo.js.org

11–20 of 97 posts

Re: JavaScript engines zoo – Compare every JavaScript engine

#12
post #2

This is super cool, I didn't know JavaScriptCore consistently outperformed V8 And SpiderMonkey seems... not up there compared to the other 2

Interesting how V8 to JSC ~2x LOC but ~2/3 the binary size.

The size difference is so large it makes me wonder if one is being compiled with ICU and the other without.

Re: JavaScript engines zoo – Compare every JavaScript engine

#14
You can see when JIT is disabled, the upcoming Static Hermes (Hermes V1) engine from Meta, built specifically for React Native, outperforms both V8 and JSCore on Apple Silicon

It'll be interesting to see how much it will affect React Native apps as it gets more and more optimized for this use case

Re: JavaScript engines zoo – Compare every JavaScript engine

#15
post #2

This is super cool, I didn't know JavaScriptCore consistently outperformed V8 And SpiderMonkey seems... not up there compared to the other 2

Disappointing for Firefox for such lower performance. I just ran the JetStream2 benchmark and got: - Firefox: 159 score - Chromium: 235 score That's on latest Fedora Linux and Ryzen 3600 CPU.

M2 Air w/ 24GB RAM macOS 26.2:

- Firefox: 253.584

- Safari: 377.470

- Chrome: 408.332

- Edge: 412.005

Re: JavaScript engines zoo – Compare every JavaScript engine

#16
post #10

I assume the 98% compatibility on ES6 for V8 is because they don't have tail call optimisation?

Maybe because with tail call optimization you wouldn't have a proper stack trace?

Supposedly, although the team at Apple were able to implement it. I think they had some oddly named technology like Chicken which created a shadow stack trace? Half remembered.

Re: JavaScript engines zoo – Compare every JavaScript engine

#20
post #2

This is super cool, I didn't know JavaScriptCore consistently outperformed V8 And SpiderMonkey seems... not up there compared to the other 2

That’s the promise of Bun - that it is faster because it uses JavascriptCore.

Bun is faster because it implements pretty much everything natively and just exposes them in JS, not because it uses JSCore

I believe long term, V8 will become the undisputed champ again as Google has a lot more incentive than Apple to make the fastest engine, but this is just a wild guess of mine, and I'm biased being a Node.js Collaborator

I've been hearing for a while that JSCore has a more elegant internal architecture than V8, and seeing the V8 team make big architectural changes as we speak seems to support it [1], but like I said, hopefully they will pay off long term

[1]

https://v8.dev/blog/leaving-the-sea-of-nodes

https://v8.dev/blog/maglev

Post reply on HN