Live data from Hacker News

JavaScript engines zoo – Compare every JavaScript engine

zoo.js.org

91–97 of 97 posts

Re: JavaScript engines zoo – Compare every JavaScript engine

#91
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.

Comments and formatting can account for that difference in LOC though... not always directly comparable. Haven't looked, but variances with different assembly bits can make a big difference too.

Re: JavaScript engines zoo – Compare every JavaScript engine

#92
post #15

Earlier quoted context omitted.

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

My results similar with M4 Pro (12 cores, 16 cores GPU), 24 GB RAM macOS 26.2 (the same benchmarks, I guess, https://browserbench.org/JetStream2.0/):

Firefox: 298.136

Safari: 425.762

Just the last test in this test suite:

> 3d-cube-SP > 3D cube rotation benchmark by Simon Speich. The original can be found on Simon's web page. Tests arrays and floating-point math in relatively short-running code.

gives the following results:

Firefox: 305.197

200 First 338.983 Worst 419.309 Average

Safari: 818.449

238.095 First 176.471 Worst 1957.237 Average

which shows that in this particular test, Safari is 2.5 times faster.

Re: JavaScript engines zoo – Compare every JavaScript engine

#93
post #88
post #86

Earlier quoted context omitted.

Mainly defence in depth. I have enormous respect for Fabrice but mquickjs is only a few weeks old and I'm no way near skilled enough to audit his C code! Running it in WASM feels a lot safer to me.

At that point why not just run V8 isolates, if JS is your only guest?

I'm having trouble finding a library for running v8 isolates from Node.js or Python doesn't include a warning in the README not to use it to run untrusted code.

Re: JavaScript engines zoo – Compare every JavaScript engine

#94
post #93
post #88

Earlier quoted context omitted.

At that point why not just run V8 isolates, if JS is your only guest?

I'm having trouble finding a library for running v8 isolates from Node.js or Python doesn't include a warning in the README not to use it to run untrusted code.

https://github.com/laverdet/isolated-vm

https://github.com/fulcrumapp/v8-sandbox

But yeah, interesting, it might not exist.

Re: JavaScript engines zoo – Compare every JavaScript engine

#95
post #22

Earlier quoted context omitted.

> Google has a lot more incentive than Apple to make the fastest engine What are those incentives? I see no incentive for Google to make something fast.

Faster page load times increases engagement with the web. More engagement on the web leads to more engagement with Google's ads.

But this was always true. True for last 40 years.

What’s changed in 2026 that will motivate Google to overtake JSCore?

Re: JavaScript engines zoo – Compare every JavaScript engine

#96
post #55

Earlier quoted context omitted.

React Native continues to be one of the best technology bets I’ve ever made. At one point I really thought that Flutter would outclass it but typical Google project stuff has really put a damper on it from all I can see. It’s not better than native apps, but as far as cross platform GuIs go it’s still very very good

Flutter and KMM are actually very good and better to use than the debacle that React Native can be. But they’re worlds behind in community support, and React Native became the ‘kitchen sink’ that works for most needs. As a React Native developer for, what, 6 years, I don’t have much positivity left to offer. Bug reports to the core team that went nowhere, the Android crash on remote images without dimensions, all the…

The problem Flutter has is highly highly dependent on Google, from funding to development.

That it is also the only real use case for Dart also doesn’t help matters.

While I agree the technology is very good and in some cases superior it doesn’t have a path to stable funding, seemingly. Google laid off a big chunk of Dart and Flutter teams last year, and there is no Expo to pickup the slack.

While Meta could do the same for React Native, Expo has always been there to pick up the slack and it receives bigger community support from the community too. For example Shopify has a few great well maintained RN libs

Re: JavaScript engines zoo – Compare every JavaScript engine

#97

Earlier quoted context omitted.

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 archit…

Bun's original marketing used JSCore's superior performance as a main benefit over Node.js.[0] Why would Google have more incentive than Apple to make the fastest engine? Safari being the fastest mobile browser is important to Apple. If Google had a stronger incentive than Apple, we would have seen V8 being more performant by now. [0] https://web.archive.org/web/20220724110148/https://bun.sh/

> Bun.js uses the JavaScriptCore engine, which tends to start and perform a little faster than more traditional choices like V8.

Little faster? Like I said, that's not a *main* benefit as it's not why Bun can be 5 to 10x faster than Node.js

Post reply on HN