Re:Extensible WASM Applications with Go
by ratorx on Friday February 14, 2025 @04:07AM
(#43046397)
I can think of a few (nothing super compelling though):
* “batteries-included” std - some of this is platform APIs, so only really the pure stuff. You can use all of this in the wasm extension, whereas you’d need to pull in deps for JS.
* “batteries-included” std - some of this is platform APIs, so only really the pure stuff. You can use all of this in the wasm extension, whereas you’d need to pull in deps for JS.
* Non-browser use cases (dynamic extensions, cross-platform “binaries”, cloud functions etc)
* probably the same reasons that JS/NodeJS became popular on the backend, but with roles reversed.