This would appear to solve so much trouble caused by JS.
More info for those interested:
Each WebAssembly module executes within a sandboxed environment separated from the host runtime using fault isolation techniques. This implies:
1. Applications execute independently, and canâ(TM)t escape the sandbox without going through appropriate APIs.
2. Applications generally execute deterministically with limited exceptions.
The design of WebAssembly promotes safe programs by eliminating dangerous features from its execution semantics, while maintaining compatibility with programs written for C/C++.
Provided this is designed & implemented with an end-user-first mentality, sign me up! If it's designed with a Facebook-shareholders-first mentality, it will trigger another Noscript update to deny webassembly reqs from unknown hosts...etc.
tl;dr: just make the web work with the end users in mind not the greedy sods