4 ms·
WebAssembly is getting more complex bit by bit...
by meindnoch 3y ago
WebAssembly is getting more complex bit by bit...
- jeffparsons 3y agoThat'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.
- charcircuit 3y agoBut they make making WASM implementations harder to make.
- phickey 3y agoUseful things are hard to make.
- kaliqt 3y agoThat'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.
- 4ad 3y agoIf you are talking about things like the garbage collection, yes, but this proposal is trivial to implement.
- davexunit 3y agoPeople 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.
- pests 3y agoThis is just a proposed extension.
- titzer 3y agoAlong 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.