@ncweaver @anildash I don't have a great solid answer for that, but the impression I've got is that WASM was helped by twenty years of lessons from the JVM and from browser development in general
Browser developers are really, really good at understanding the challenges involved in executing code from untrusted sources!
@simon @anildash
I think that may be it. The JavaScript JITs are insane, and that they aren't subject to more OMG breakages, and the browsers these days split the rendering engine per origin into a separate process (with all the process isolation on top), the browser folks have a lot of experience.
Also, I think WASM started much smaller, and the only outside world is through the JavaScript framework rather than direct probably helps too.