Btw deactivating WebAssembly support in Chrome 63 (up-to-date) doesn't work anymore!!
chrome://flags/#enable-webassembly
Setting it to "deactivated" does nothing, WebAssembly is still active.Btw deactivating WebAssembly support in Chrome 63 (up-to-date) doesn't work anymore!!
chrome://flags/#enable-webassembly
Setting it to "deactivated" does nothing, WebAssembly is still active.Just wait until it gets a bit more mature.
It will be the same fun as when Ads moved away from Flash into HTML 5/JavaScript.
That said, it will lead to more closed commercial sites, but the JS outputted from webpack+babel+uglify is already unbelievably difficult to wade through without source maps. It's not significantly different imho.
afaik, wasm is not 'binaries' in that it's not an arbitrary blob of machine code fed right into the cpu. it's still running in a sandbox (a la javascript) including similar limitations wrt CORS etc.
https://www.chromium.org/Home/chromium-security/ssca
https://blog.mozilla.org/security/2018/01/03/mitigations-lan...
WASM is portable binaries.
People frequently make this comparison upon hearing the term sandbox, but this is a weak comparison. Yes JavaScript executes in a sandbox, but the JavaScript (JIT) sandbox is purely for performance instead of isolation, which is like comparing a pencil sharpener to a bulldozer just because they are both portable machines. A better comparison of the JavaScript (JIT) sandbox is the JVM.