WASI Support in Go
Can someone hit me with the value proposition of all this WASI stuff and WASM and ELI5? (I get the browser use-case)My understanding is as follows:  WASM - a portable, platform-independent virtual machine for executing a "web assembly"

  WASI - an extension to the virtual machine that adds APIs for interacting with the system and breaks all the WASM sandboxing (presumably NOT platform-independent?)

Is the point of this addition to Go that I can now target "WASM implementations that have WASI" with Go source code compiled to WASM?Why would someone want to do that? Just for edge functions in cloud workers?