WebAssembly

“If you need games in the browser or stuff where every byte needs optimization go with WASM”

“WASM is not memory safe in the same sense, in particular, heap corruption vulnerabilities still exist”

“only not as breakthrough as it gets advertised given how many bytecode formats have existed since 1958”

“Personally I've run Python + Sympy, Xcas/Giac and Maxima in the browser through this amazing tech.”

“WASM is stuck in zone between living and the dead - just good enough (barely) to merit creating production code”

“There's also an 'escape hatch' with WebAssembly for better performance when you need it.”

“it is actually better for long-term archival: you dont need to carry decompression program”

“I like the technical design of WASM, but I feel that better OS sandboxes for regular native code will be the common approach”

“with wasm you have the wasm file which you need to load on the side, which is a bit clunkier”

“WASM was built from the ground up with a standards process and multiple implementations.”

“Wasm evolves slowly and deliberately, and IMO hasn't made any massive fatal design errors yet”

“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”

“WASM was designed from the ground up as CPU agnostic bytecode that's also much easier and faster to validate.”

“I like WASM and I want to like WASM but the rate of maturity within the ecosystem is incredibly abysmal.”

“designed by a broad group of stake holders with lessons from past plugin and VM systems”

“It's "just another" virtual instruction set, and for that it turned out pretty great.”

“If something like WASM existed at the time to make it possible for them to run fully inside the sandbox”

“wasm is perfect for this, its almost native speed, built for security and language neutral”

“WebAssembly is designed to not have that limitation: it's much more closely aligned to JS.”

“WASM is generally interpreted -- you can compile it, but it wasn't really designed for that as far as I know.”

“then WASM can be incredibly useful, e.g. all my C/C++ projects are running automatically in browsers thanks to wasm”

“WebAssembly is amazing, but I don't think making it a DOM controller is where the action is.”

“in my experience wasm (from rust) tends to be faster then then hand-written js for the same function”

“creating plugins that get executed in the browser to render files like Parquet, PSD, TIFF, SQLite”

“It is a wonderful tool and it is a truly magical feeling to see my native games running in the browser.”

“Being able to compile mature and well-tested libraries into WASM instead of trying to find a JS equivalent is incredible value.”

“Being able to write-once and compile for the web and desktop felt like the future.”

“That's exactly why we chose wasm for minfx.ai, I didn't want to touch JavaScript with a yard stick”

“it has been a huge success despite not yet reaching bare-metal levels of performance and energy efficiency”

“it was certainly an impressive achievement, it was clear to me that the technology friction was mostly on how it was integrated”

“it is deterministic and can be used to build decentralized smart contracts and Byzantine Fault Tolerant distributed systems”

“in an apples-to-apples comparison WebAssembly is significantly faster to start than JavaScript”

“Where it has worked is as infrastructure: fast, sandboxed, portable code for the parts that actually need it.”

“I keep feeling like the folks behind WASM are just totally neglecting the obvious gap in the stack”

“Only really heavy use cases like media editing or Figma-like apps really benefit from what WASM has to offer.”

“being told web assembly helps some parts of Figma run faster feels like a big let down”

“it's a lot quicker and easier to write the code in #1 than #2 and it is easier to maintain as well”

“Warm was great because it was lightweight and easy to target from any language and create any custom interaction API with the host.”

“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”

“you're generally going to be adding headache (build tooling, wrangling data between languages and runtimes, etc.) rather than removing it.”