lucet VS libfringe

WebAssembly is extremely portable. WebAssembly runs on: all major web browsers, V8 runtimes like Node.js, and independent Wasm runtimes like Wasmtime, Lucet, and Wasmer.

The bytecode alliance had the lucet project which would be an OS executing WASM application, enabling very strict sandboxing.

References for anyone following: wasmtime Lucet

I guess lucet could be an under-layer for this but it's not really the same, different levels of the stack. Fascinating.

I also want to use this opportunity to say a big thank you to the teams working on Rust, Wasmer, Wasmtime, Lucet and waSCC. It would be impossible to build Lunatic without all the hard work put into this projects.

There’s a bunch of library-based implementations of coroutines for rust. I recall https://github.com/edef1c/libfringe being the most interesting one, but it is quite dated. I don’t think there’s a lot of community interest in stackfull coroutines at this point.

As we saw earlier, scheduling threads is a hard task for the operating system. To replace one thread that's being executed with another one, a lot of work needs to be done (including saving all the registers and some thread state). However, switching between Lunatic Processes does only the minimal amount of work possible. With an idea pioneered by the libfringe library and using some asm! macro magic, Lunatic lets the Rust compiler figure out the minimal number of registers to be preserved during context switches. This makes scheduling Lunatic processes zero-cost. On my machine usually 1ns, equivalent to a function call.