3 ms·
I've always been curious why WASM has the program flow restrictions it has. Most "ASM" just lets you set whatever register. There isn't much sandboxing value (
by gary_0 3y ago
I've always been curious why WASM has the program flow restrictions it has. Most "ASM" just lets you set whatever register.
There isn't much sandboxing value (WASM shouldn't be able to touch addresses outside the sandbox anyways). Was the reason ease of compilation/optimization for arbitrary architectures? Easier to run inside an interpreter?
The default idea for WASM feels like it should have been more like RISC-V (but with enough wiggle-room to allow easy JITing to x86/ARM).
Or are most of WASM's quirks just because it has ASM.js in its lineage?