Re:Web Assembly Working Group Charter Approved
by baybal2 on Saturday August 05, 2017 @04:00AM
(#14934689)
You are unaware of issues with sandbox.
Here they are:
1. A sandbox can have bugs, and they do have them
2. Sandboxed environments have to give huge reach of system api's anyways, and you can do a lot with them
3. There are classes of vulnurabilities that sandboxes can't do anything about: instruction level exploits, hardware bugs, "gpu frying webgl shaders"
4. Human factor (see comments about "run anyways" above)
Re:Web Assembly Working Group Charter Approved
by Houshalter on Saturday August 05, 2017 @06:40AM
(#14935112)
All of that applies to JavaScript again. Wasm is just lower level and simpler. If anything it should be significantly easier to sandbox because of its simplicity. It doesn't provide any more access to Apis or anything than JavaScript does.
Wasm is the first time we will get cross platform and fully sandboxed native speed code.
None of what you speak of has anything to do with wasm. You can do all that just fine with JavaScript. We've had that world ever since browsers allowed disabling right clicking. Even before js, you could always distribute your webpage as an image if you wanted that. Wasm just let's you run code faster. It doesn't change anything.