News for hackers. Stuff that matters.

A comment on Making WebAssembly a first-class language on the Web. Parent comment

Re:Making WebAssembly a first-class language on the Web by Retr0id on Wednesday March 11, 2026 @02:37PM (#47339428)
On one hand, yes, new attack surface is new attack surface. But WASM has been in browsers for almost a decade now.
[ Parent | on HN ]
Re:Making WebAssembly a first-class language on the Web by lich_king on Wednesday March 11, 2026 @02:56PM (#47339681)
Without the bindings this talks about, so it really couldn't do nearly as much.
[ Parent | on HN ]
Re:Making WebAssembly a first-class language on the Web by 0x457 on Wednesday March 11, 2026 @08:13PM (#47344457)
WASM has access to everything JS has via JS in the same sandbox that JS runs in.

JS didn't magically become more "secure". Multiple things happened:

- ActiveX and Flash got booted from browsers

- Browsers got much better sandboxes

Essentially limited what untrusted code can run and sandboxed that untrusted code. Before NaCl and PNaCl it was wild west in browsers.

The same sandbox runs WASM. It even goes through the same runtime in every browser. It's no different from compiling language of your choice to subset of JavaScript (see asm.js).

[ Parent | on HN ]