4 ms·

Potentially stupid question: I can see the benefit of running Go-compiled-to-WASM client side but I don't really get why I might want to run WASM server-side.

Potentially stupid question: I can see the benefit of running Go-compiled-to-WASM client side but I don't really get why I might want to run WASM server-side. What would be the benefit of server-side WASM over running a Go binary directly? To run untrusted binaries alone or are there other benefits?

debarshri 4y ago
WASM is often pitched as a potential alternative to docker and other OCI compatible alternatives. It does not have to be a go-compiled-to-wasm, it could be python compiled to WASM, or rust for that matter. Either ways, you could use any function runners like these, Wasmer [1] or any webassembly runtime to run them on a host. [1] https://wasmer.io/ https://wasmer.io/
- TobyTheDog123 4y ago
  Isn't Wasmer the sketchy one? I'm not very up-to-date on the WASM drama lately.
  - debarshri 4y ago
    I'm not aware of one. Is there some WASM drama going on lately?
    - ignoramous 4y ago
      https://news.ycombinator.com/item?id=27543731 https://news.ycombinator.com/item?id=27543731
0x457 4y ago
WASM on server-side main benefits are: easy sandboxing, being polyglot, hot-reload. This one seems not quite polyglot, but it's easy to change. I think WASM, once WIT (or something similar) gets into spec, will be a wonderful way to make plugins for your service.