# WebAssembly

116 Hacker News commenters recommended WebAssembly and 60 criticized it, November 2025 to November 2026. It was recommended in 13 of 13 months.

**Verdict:** A fast, sandboxed, portable compile target that lets C, C++ and Rust code run in the browser, though critics cite immature tooling, clunky JavaScript interop and limited memory safety.

## Why people recommend it

- Runs native code in browsers (6 comments): "Being able to compile mature and well-tested libraries into WASM instead of trying to find a JS equivalent is incredible value." ([source](https://news.ycombinator.com/item?id=46553485)) "then WASM can be incredibly useful, e.g. all my C/C++ projects are running automatically in browsers thanks to wasm" ([source](https://news.ycombinator.com/item?id=47296601)) "It is a wonderful tool and it is a truly magical feeling to see my native games running in the browser." ([source](https://news.ycombinator.com/item?id=46690085))
- Near-native, fast performance (5 comments): "it has been a huge success despite not yet reaching bare-metal levels of performance and energy efficiency" ([source](https://news.ycombinator.com/item?id=46551981)) "in my experience wasm (from rust) tends to be faster then then hand-written js for the same function" ([source](https://news.ycombinator.com/item?id=46860727)) "in an apples-to-apples comparison WebAssembly is significantly faster to start than JavaScript" ([source](https://news.ycombinator.com/item?id=46551591))
- Sandboxed and portable (4 comments): "Warm was great because it was lightweight and easy to target from any language and create any custom interaction API with the host." ([source](https://news.ycombinator.com/item?id=46262654)) "Where it has worked is as infrastructure: fast, sandboxed, portable code for the parts that actually need it." ([source](https://news.ycombinator.com/item?id=46551509)) "WASM was designed from the ground up as CPU agnostic bytecode that's also much easier and faster to validate." ([source](https://news.ycombinator.com/item?id=48209252))
- Carefully designed open standard (4 comments): "Wasm evolves slowly and deliberately, and IMO hasn't made any massive fatal design errors yet" ([source](https://news.ycombinator.com/item?id=48211789)) "WASM was built from the ground up with a standards process and multiple implementations." ([source](https://news.ycombinator.com/item?id=48213048)) "designed by a broad group of stake holders with lessons from past plugin and VM systems" ([source](https://news.ycombinator.com/item?id=47935702))

## What people warn about

- Immature ecosystem and tooling friction (5 comments): "you're generally going to be adding headache (build tooling, wrangling data between languages and runtimes, etc.) rather than removing it." ([source](https://news.ycombinator.com/item?id=45856491)) "I like WASM and I want to like WASM but the rate of maturity within the ecosystem is incredibly abysmal." ([source](https://news.ycombinator.com/item?id=48208937)) "it was certainly an impressive achievement, it was clear to me that the technology friction was mostly on how it was integrated" ([source](https://news.ycombinator.com/item?id=46551754))
- Clunky JavaScript and host interop (3 comments): "you're generally going to be adding headache (build tooling, wrangling data between languages and runtimes, etc.) rather than removing it." ([source](https://news.ycombinator.com/item?id=45856491)) "With wasm, I could pass a Uint8Array out of it. If I wanted to pass it in, I had to call malloc from the javascript side" ([source](https://news.ycombinator.com/item?id=48210334)) "with wasm you have the wasm file which you need to load on the side, which is a bit clunkier" ([source](https://news.ycombinator.com/item?id=48213229))
- Not fully memory safe (2 comments): "WASM is memory safe in that you can't escape the runtime. It's not memory safe in that you can escape the program running within the sandbox" ([source](https://news.ycombinator.com/item?id=46260926)) "WASM is not memory safe in the same sense, in particular, heap corruption vulnerabilities still exist" ([source](https://news.ycombinator.com/item?id=49309686))
- Only pays off for heavy apps (2 comments): "being told web assembly helps some parts of Figma run faster feels like a big let down" ([source](https://news.ycombinator.com/item?id=46551217)) "Only really heavy use cases like media editing or Figma-like apps really benefit from what WASM has to offer." ([source](https://news.ycombinator.com/item?id=46551294))

## Cite as

Hacker Approved, "WebAssembly", https://hackerapproved.com/p/webassembly/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).