Hacker News Reader

That's okay; _using_ WebAssembly is getting easier bit by bit. Features like this one allow the high level programming language features you know and love to be implemented efficiently behind the scenes.

But they make making WASM implementations harder to make.

Useful things are hard to make.

That's how the core has to be, like Vulkan, making the core harder allows for more control, a better foundation. Then we load up those core libraries with easy APIs that are super powerful and can do what was never thought possible.

Same for WebGPU.

So I think WASM is doing this exactly the right way as long as it stays powerful and flexible at the core.

If you are talking about things like the garbage collection, yes, but this proposal is trivial to implement.

People said this about GC but then I implemented a WASM interpreter with GC support and it wasn't very hard to do. This FX proposal would introduce... 6 more instructions I think? Not bad. Especially compared to something like the SIMD extension which feels like it's adding a million instructions.

Along with exception handling, I think a stack switching feature like WasmFX will complete WebAssembly's set of control abstractions, so at least that part won't keep growing without bound.

This is just a proposed extension.