Hacker News Reader

Comment by qwertox | Hacker News Reader

That's great news! I thought the project had died and that this meant that V8 was the only serious JavaScript engine for the future.

For those who don't know: "Servo is a web browser rendering engine written in Rust, with WebGL and WebGPU support, and adaptable to desktop, mobile, and embedded applications."

View on HN

I'm confused: why would the existence of a browser engine affect a JavaScript engine? Don't you mean WebKit/Blink instead of V8?

Either way I'm glad that there's a challenge to the browser monopoly and its various technical components of course.

Servo just uses SpiderMonkey instead of their own JS engine in Rust.

Even without SpiderMonkey, we'd still have JavascriptCore from Safari and LibJS from Ladybird.

And some lightweight alternatives like Bellard's QuickJS (https://bellard.org/quickjs/) in C and Kiesel (https://kiesel.dev/) in Zig.

Also, Hermes which React Native uses.

AWS' LLRT runtime just switched to QuickJS-NG [0]

0. https://github.com/awslabs/llrt/pull/669

I don't see the relevancy of the JS engine in the context of a web rendering engine and its independent complexity. The homepage of Servo (basically, a portion of the Wikipedia entry snapshot) doesn't even mention it.

Because the parent-most post from quertox was:

> That's great news! I thought the project had died and that this meant that V8 was the only serious JavaScript engine for the future.

The person you're responding to was basically clarifying what you want to too.

> V8 was the only serious JavaScript engine for the future.

Firefox's SpiderMonkey? Webkit's JSC?

spidermoneky has been around since before V8

Bit of an understatement. SpiderMonkey was the first JavaScript engine (out of all of them), born in 1996, made by refactoring the scraps of Mocha that was the initial prototype made by Eich.

I thought it had died too. Great to see it make a comeback.

Reply on news.ycombinator.com