alt Hacker NewsBun 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]
Replies
For a long time v8 was the fastest on a set of benchmarks but not on real world work load. That was the time when SpiderMonkey and JSC decided to go on a different path. I believe it was Mozilla that make the move first.
If we believe there is limit to everything, then the only sane conclusion would be v8 and JSC would both perform nearly the same with negligible difference in the long term. So choosing something that is fast, simple to integrate now makes a lot more sense.
Of course that is assuming memory usage, security and others being equal.
> 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.
I am not sure how "long term" you are thinking about. Making big architectural changes does not necessarily lead to better performance. JSC has been the fastest JS engine in the past 5-10 years as I remember. If google had a solution, they would have it now.
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/