But at the end of the day, engineering is about finding the right tradeoffs to your problems. Prescriptively denying the existence or fitness of other solutions to all problems is an anti pattern

Where you need hard real-time responses, maybe a cooperative system is not the easiest to analyze, maybe there a good old super loop is fine if your system is simple enough.

if you need ARINC653 partitioning, you’d reach for something like hubris, and build on top to guarantee time partitioning

I resonate with this view as well. For the kind of embedded systems most people build (iot), async hides explicit state machines and event loops. Some systems do need a higher degree of fault isolation and there hubris is a fit.

More guarantees need to be upheld in Rust, like aliasing between a `&mut T` and `&T`. These are handled conservatively in Zig, but Rust chooses to optimize the fact that they cannot be aliased. That said, I am concerned about this rewrite for other reasons than the unsafe Rust.