WebAssembly
No written verdict yet. Here is what commenters said.
Why people recommend it
“I'd love to see CHERI (for the room) and Wasm take off”
“Wasm's guarantees are incredibly strong and formally proved”
Show 3 more
“Its technical design is a solid foundation, a lot of good thought went into it”
“WASM code pretty much runs at native speed these days”
“using WASM can minimize cold startup time for serverless functions”
Caveats and dissent
“It is mostly a solution looking for a problem”
“The WASM GC standards team was warned in advance that the proposal wouldn't work for .NET, and they moved forward with it anyway”
Show 2 more
“WASM programs could theoretically just run forever in entirely reasonable cases”
“nobody is really using it”
Often compared with
From the makers not counted in the ranking
“I am co-champion of a proposal to fix this”
Threads where it came up
- What Happened to WebAssembly 4 mentions
- Saying Goodbye to Asm.js 3 mentions
- Nominal Types in WebAssembly 3 mentions
- Increasing the performance of WebAssembly Text Format parser by 350% 3 mentions
- Making WebAssembly a first-class language on the Web 2 mentions
- Notes on Writing WASM 2 mentions
Data: webassembly.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 28
“It is mostly a solution looking for a problem”
“The WASM GC standards team was warned in advance that the proposal wouldn't work for .NET, and they moved forward with it anyway”
“I'd love to see CHERI (for the room) and Wasm take off”
“WASM programs could theoretically just run forever in entirely reasonable cases”
https://ssheasy.com/ https://www.google.com/search?q=wasm+ssh+client ...the future is here!
“WASM was designed from the ground up as CPU agnostic bytecode”
“asmjs is going to be strictly more limited in interacting with JS than wasm”
“Wasm's guarantees are incredibly strong and formally proved”
“nobody is really using it”
“Its technical design is a solid foundation, a lot of good thought went into it”
“WASM code pretty much runs at native speed these days”
“using WASM can minimize cold startup time for serverless functions”
“I think the Wasm network effect is happening, it is just very slow”
“We use WASM to deploy machine learning models in the browser”
“then WASM can be incredibly useful”
“I just don't see that as a viable alternative to the web mess that we already have.”
“WASM components [1] is a spec that tries to improve on this with an IDL called WIT”
“I am happy you and the team added GC to WebAssembly.”
“It also simply lets you use rust on the web. That's why I use wasm.”
“is much, much faster at 16k renders then Javascript”
“I use a wasm xxhash implementation that is 40x faster than the fastest JavaScript version”
“No, WASM is deterministic, JS is fundamentally not.”
“Fundamentally I think asm.js was a fragile hack and WASM is a well-engineered solution.”
“it has been a huge success despite not yet reaching bare-metal levels of performance and energy efficiency”
“WebAssembly itself is not that inefficient in storage.”
Is WASM’s story for side effects solved yet? eg network calls seems too complicated (https://github.com/vasilev/HTTP-request-from-inside-WASM etc)
“can be configured to be a lot simpler than WASM”
“WASM lacks native threading”