> If one writes Go or Rust, there are much better ways to run them than targeting WASM wasm has its place, especially for contained workloads that can be wrapp

> If one writes Go or Rust, there are much better ways to run them than targeting WASM wasm has its place, especially for contained workloads that can be wrapped in strict capability boundaries compile-time (think, file-encoding jobs that shouldn't access anything else but said files: https://news.ycombinator.com/item?id=29112713 https://news.ycombinator.com/item?id=29112713). > Containers are still the defacto standard. afa FaaS is concerned, wasmedge [0], atmo [1], tarmac [2], krustlet [3], blueboat [4] and numerous other projects are turning up the heat [5]! [0] https://github.com/WasmEdge/WasmEdge https://github.com/WasmEdge/WasmEdge [1] https://github.com/suborbital/atmo https://github.com/suborbital/atmo [2] https://github.com/madflojo/tarmac https://github.com/madflojo/tarmac [3] https://github.com/krustlet/krustlet https://github.com/krustlet/krustlet [4] https://github.com/losfair/blueboat https://github.com/losfair/blueboat [5] https://news.ycombinator.com/item?id=30155295 https://news.ycombinator.com/item?id=30155295