okapi VS not-yet-awesome-rust

It's inspired by others in the space that you might check out: paperclip, okapi, and others.

okapi: supports rocket

okapi looks decent as well. Has codegen for Rocket: https://github.com/GREsau/okapi

I have used it the other way around. I created the Rust code and using that to generate the documentation. https://github.com/GREsau/okapi this worked very good. Here is the generated documentation: https://docs.dfstoryteller.com/rapidoc/ This uses the Rust Doc comments to populate the documentation.

Oh Rocket, you playful muse. I've watched you ascend from my early Rust days; yet each time I reach for you my heart sinks more. This research project of mine led me to okapi, an extension for OpenAPI documentation. And yet, I have to pass once again. While most of the Rust ecosystem blazes toward async, you inch toward it too slowly. Perhaps next time I search for a web framework our paths will align, but until then, I must follow a different orbit.

https://github.com/not-yet-awesome-rust/not-yet-awesome-rust might give ideas

My suggestion would be to find something on Not Yet Awesome Rust that is not ARM-specific, but would be useful on ARM, and which interests you, and then do that.

For a wishlist, you can check Not Yet Awesome Rust or Not Yet Awesome Embedded Rust.

Maybe take a look at Not Yet Awesome Rust? (A list of libraries people want in Rust but which don't exist yet.)

Aside from that, there's always Not-Yet-Awesome Rust. (Check the issues too. The README is lagging behind.)

hostapd

Not Yet Awesome Rust