Markus Eisele
Wasm's Identity Crisis: What the 3.0 Release Tells Us About WebAssembly's Uncertain Future https://redmonk.com/kholterhoff/2025/10/17/wasms-identity-crisis/
#wasm #redmonk
Wasm's Identity Crisis: What the 3.0 Release Tells Us About WebAssembly's Uncertain Future

WebAssembly 3.0 dropped, and the developer community has some thoughts. Business as usual on the internet, right? Sure, but this update to the specification also dredges up ongoing questions about the purpose and identity of WebAssembly (Wasm) that are worth revisiting. Born from the ashes of Mozilla’s asm.js and Google’s Native Client in 2015, two

console.log()
Oct 17 at 8:58pmWeb
Show threadChristof PetigOct 17
@myfear nicely level headed article, just skip the doom laden headline to get to the interesting information.
I personally eagerly wait for the features which are coming soon... repeatedly once they became reality...
Show threadtshepangNov 17
@christofp what are some of those features
Show threadChristof PetigNov 17

@tshepang multi threading, c++ exceptions and dynamic allocation free strings and lists for the component model.

Sy has started cooperative threading in wasmtime, exceptions need a small fix to the sdk and Luke just presented about reducing allocations at WasmCon (I eagerly await to watch the talk on YouTube).

I guess we will find a good way to make allocation free components happen as my existing independent (?) example implementation for shared memory buffers is another option to solve this. Perhaps you can combine them with gc in a cool way.