lasiotus

I've been working on Motor OS for almost five years now. In May during the short Fable window it helped me find and fix a race that I've been debugging for about three months. Since July (when Fable, and later Astra) became available, most items on the roadmap have been fixed. What it would take me ~ 3 months doing myself (evenings and weekends), LLMs complete in about a week (with supervision; even Fable MAX and Astra MAX need supervision when doing critical low-level stuff).

gVisor is... less secure than VMs; but the front page price-compares against VMs, so not apples-to-apples

Unikernels are on the smaller side of the spectrum; Linux on the larger side, with a lot of room in the middle...

Is there anything like this but in TUI?

Motor OS is now a Tier-3 target in Rust.

> If anything does present a concrete issue we are eager to address it.

That's great to hear! I think it is a bit too early to spend extra effort on porting Wasmtime to Motor OS at the moment, as there are a couple of more pressing issues to sort out (e.g. FS performance is not yet where it should be), but in a couple of months I may reach out!

I'm not the OP, but I have a similar experience with Motor OS: wasmi compiles and works "out of the box", while wasmtime has a bunch of dependencies (e.g. target-lexicon) that won't compile on custom targets even if all features are turned off in wasmtime.

Motor OS