3 ms·
There's no reason to suspect that browser implementors would sandbox wasm any less strictly than JS. Heck, there's no reason to suspect that they wouldn't just
by kibwen 11y ago
There's no reason to suspect that browser implementors would sandbox wasm any less strictly than JS. Heck, there's no reason to suspect that they wouldn't just re-use the existing JS sandbox.
- BrendanEich 11y agoThanks, kibwen. I'll make a stronger statement. By definition, wasm and JS are two syntaxes (initially co-expressive, wasm and asm.js) for one VM. Do people actually read docs any longer? https://github.com/WebAssembly/ https://github.com/WebAssembly/ has some, my blog covered the 1VM requirement. There won't be a new "sandbox". JS and wasm interoperate over shared objects.
- girvo 11y ago> Do people actually read docs any longer No, not really. People read headlines and make pithy middlebrow comments. Though I also don't think that's a new phenomenon...
- _alexander_ 11y ago> Do people actually read docs any longer? No. People only read headlines that WebAssembly is replacement for JS ;)