News for hackers. Stuff that matters.
Re:QuickJS, the Next Generation: a mighty JavaScript engine by rfoo on Monday July 08, 2024 @02:58AM (#40903176)
> Is there anywhere it's a clearly better choice?

Embeddable use when you need latest ECMAScript support.

> Does it have a shot of being a top class engine?

No.

Re:QuickJS, the Next Generation: a mighty JavaScript engine by akie on Monday July 08, 2024 @03:26AM (#40903313)
Why does it not have a shot of being a top class engine?
Re:QuickJS, the Next Generation: a mighty JavaScript engine by masklinn on Monday July 08, 2024 @03:55AM (#40903447)
Because the main goals are to be small, embeddable, and have low startup time.

A top class engine requires a JIT and that generally leads to being large and having high startup time. LuaJIT is pretty much the exception which proves the rule and 1. Mike Pall is a monster of a developer not unlike Bellard; and 2. Pall is on record (in discussions with other JIT people) that in his opinion you can’t bolt a JIT to an existing runtime and get a maximally efficient JIT. So you’d need someone of that class of skill to decide to make that their legacy.

Re:QuickJS, the Next Generation: a mighty JavaScript engine by lifthrasiir on Monday July 08, 2024 @04:22AM (#40903576)
And it's not like that Bellard is unable to produce a JIT compiler; see, for example, QEMU dyngen [1] which eventually inspired CPython's new JIT compiler.

[1] https://www.usenix.org/legacy/event/usenix05/tech/freenix/fu...

Re:QuickJS, the Next Generation: a mighty JavaScript engine by petters on Monday July 08, 2024 @03:32AM (#40903333)
Performance
Re:QuickJS, the Next Generation: a mighty JavaScript engine by rfoo on Monday July 08, 2024 @06:24AM (#40904151)
Like other replies said, having JIT requires quite different tradeoffs to be made.

And unfortunately, making a very fast interpreter-based JS engine is a tedious and human-power-heavy work, it involves a lot of work which can't be eliminated by better skills.