Thank you very much!

I totally agree on reinventing the wheel. I think our biggest tool towards that will be Node-API, which is the one low-level building block that JavaScript runtimes seem to agree on (and heck, I'm sure non-JavaScript engines could implement a decent chunk of Node-API). The Hermes team are currently interested in it (https://github.com/facebook/hermes/pull/1377#issuecomment-29...) for implementing heavy chunks of the ECMAScript spec like Intl and Temporal as plug-in features.

It's interesting that you bring up tooling like npm and Cargo, I've never thought of sharing those. Although I'm no great shakes at Rust, I really, really liked how Cargo did things (e.g. optional dependencies and rigid library structure) and it'd be incredible to have that for the JavaScript ecosystem.

Also do keep hearing nothing but great things about Graal, I think it's being slept on.

▲

serhalp 4 days ago | parent [-]

> I really, really liked how Cargo did things (e.g. optional dependencies and rigid library structure) and it'd be incredible to have that for the JavaScript ecosystem.

FYI: https://thenewstack.io/vites-creator-on-a-unified-javascript...

	▲	LinguaBrowse 3 days ago \| parent [-]
		I'm keeping my eye on Void0, yeah! If anyone can live up to such promises, it'll be them. They'll have a tough job getting sticky ecosystems like React Native to adopt, but hope to see them make a compelling case for their stack.