js-compute-runtime

it's sad that they didn't go the same way than fastly which actually use a wasm runtime even for javascript by compiling spidermonkey to wasm: https://github.com/fastly/js-compute-runtime I think thats way more clever than having a mixed runtime. and they use wizer to make it more performant.

These are good questions! Here's some answers from the corner of the world I know best as a Wasmtime contributor at Fastly: 1. Spidermonkey.wasm is the basis of Fastly's JavaScript on Compute@Edge support. We have found it to be faster than QuickJS. The source code is here: https://github.com/fastly/js-compute-runtime. 2. Fastly Compute@Edge is built on wasmtime. You can develop web services for it in Rust, JS, and Go: https://developer.fastly.com/learning/compute/ 3. Fastly's multi-tenant platform is closed source, but our single-tenant local development platform, which also uses wasmtime under the hood as well, is open source: https://github.com/fastly/viceroy. It isn't a big leap to make viceroy multi-tenant: Wasmtime provides everything you need, and all Viceroy would have to do is dispatch on e.g. HTTP host header to the correct ten

btw. for what it's worth their javascript to wasm is opensource: - https://github.com/fastly/js-compute-runtime - https://github.com/tschneidereit/spidermonkey-wasi-embedding and besides that it is slower than nodejs it is still plenty fast (no matter that it is not as fast as they want) btw. it's startup is faster than node. (maybe better pgo might help) its insane what they built, to do it and it will bring the whole wasm community forward if they succeed (and I hope they do)