I am kind of worried that the eagerness for more WASM features may irremediably harm the young ecosystem. Most of what Go added to WASM could be done natively if the component model proposal [1] was merged already.
The standard evolves slowly and as adoption rises we risk having to support more and more non-standard features forever, like WASI and now this.
The standard evolves slowly and as adoption rises we risk having to support more and more non-standard features forever, like WASI and now this.
[1] https://github.com/WebAssembly/component-model