First major adopter of the new Sandbox API? Some very good tech comments happening in the last thread on Kuasar. https://news.ycombinator.com/item?id=35649189

First major adopter of the new Sandbox API? Some very good tech comments happening in the last thread on Kuasar. https://news.ycombinator.com/item?id=35649189 https://news.ycombinator.com/item?id=35649189 It was a bit surprising to me that the model is a forking model, that each VM is it's own process. Got a great reply on that: > It is very insightful to point out that forking a wasm runtime may not be the best choice, actually this is because we chose the WasmEdge as our first supported wasm runtime, and it do not support redirecting the standard io fds, so we can only fork a new process and redefine the stdin/stdout/stderr to the named pipe. we already submit an issue to WasmEdge community, we may change the fork way to starting directly. For Wasmtime (we will support it later), there is no such constraint, and we will start runtime directly. Other good discussion on how much people appreciate getting away from the much higher overhead per-container Shim v2 model! It strikes me that this could be an excellent starting place for a CloudFlare workerd js/wasm provider too. That's been a pet desire of mine, and this could drastically slash the effort required to experiment. https://github.com/cloudflare/workerd https://github.com/cloudflare/workerd It's awesome to see thr container model maturing. Much better runtime behavior here. And the ability to nicely go beyond mini-Linux-containers into new frontiers is hella exciting.