I wonder why V8 is considered as superior compared to WASM for sandboxing.

Is WASM’s story for side effects solved yet? eg network calls seems too complicated (https://github.com/vasilev/HTTP-request-from-inside-WASM etc)

▲

skybrian 8 hours ago | parent | prev [-]

On V8, you can run both JavaScript and WASM.

▲

buremba 8 hours ago | parent [-]

Theoretically yes, but CF workers or this project doesn't support it. Indeed none of the cloud providers support WASM as first-party support yet.

▲

justincormack 7 hours ago | parent | next [-]

Workers does support wasm https://developers.cloudflare.com/workers/runtime-apis/webas...

	▲	buremba 7 hours ago \| parent [-]
		Maybe it's better now but I wouldn't call this first-class support, as you rely on the JS runtime to initialize WASM. The last time I tried it, the cold start was over 10 seconds, making it unusable for any practical use case. Maybe the tech is not there but given that WASM guarantees the sandboxing already and supports multiple languages, I was hoping we would have providers investing in it.

▲

max_lt 2 hours ago | parent | prev | next [-]

CF Workers does support WASM. We do too as V8 handles it natively. Tested it, works, just hasn't been polished yet.

▲

otterley 8 hours ago | parent | prev [-]

The problem is that there’s not much of a market opportunity yet. Customers aren’t voting for WASM with their wallets like they are mainstream language runtimes.