wasmi

> Every iteration of the loop polls the network and input drivers, draws the desktop interface, runs one step of each active WASM application, and flushes the GPU framebuffer. This is really interesting and I was wondering how you implemented that using Wasmi. Seems like the code for that is here: https://github.com/Askannz/munal-os/blob/2d3d361f67888cb2fe8... It might interest you that newer versions of Wasmi (v0.45+) extended the resumable function call feature to make it possible to yield upon running out of fuel: https://docs.rs/wasmi/latest/wasmi/struct.TypedFunc.html#met... Seeing that you are already using Wasmi's fuel metering this might be a more efficient or failure proof approach to execute Wasm apps in steps. An example for how to do this can be found in Wasmi's own Wast runner: https://github.com/wasmi-labs/wasmi/blob/0198065

I see [1], thanks for sharing. I'll need to dig a bit deeper in your implementation! [1] https://github.com/wasmi-labs/wasmi/blob/master/crates/wasmi...

This looks to have come out of a blockchain company: https://github.com/wasmi-labs/wasmi/blob/master/NEWS.md#anno... I think smart contract execution is a good application of WebAssembly. It seems promising!

> Wasmi intentionally mirrors the Wasmtime API on a best-effort basis How does that correspond to implementing the wasi api? I think wasmtime is a javascript project for wasm on the web, is that a distinct thing to wasi? (this file existing suggests wasmi contains an implementation of wasi https://github.com/wasmi-labs/wasmi/blob/master/crates/wasi/...)