MoonZoon VS smol

They are both async and made for GUI -- in case of rust-signals WebGUI, provided by dominator and MoonZoon.

Fullstack Framework: MoonZoon, Leptos

Dominator is more of a low-level framework for manipulating the DOM. There's also MoonZoon (https://github.com/MoonZoon/MoonZoon) which uses dominator but provides a more complete experience.

Alternative 2)thin client in browser and server in rust. If you really want to limit it to web client and web server, possibly try a newer approach with moonzoon. https://github.com/MoonZoon/MoonZoon/tree/main/examples/todomvc

I don't really know Rust so clearly I'm not the target audience, but this thing where you define all the styles using chains of methods seems kinda clumsy to me. And if it's all turning into CSS in the end you presumably still need to understand CSS concepts in order to make the layout you want using this syntax. So I'm not sure this is really saving you from learning HTML and CSS. That said it does appear to be compiling your Rust to web assembly (like Blazor does) which is pretty cool.

I've come across MoonZoon (https://github.com/MoonZoon/MoonZoon) which seems like an interesting full stack framework, but I'm wondering about a solution that would allow choosing both frontend and backend frameworks.

There’s also https://github.com/MoonZoon/MoonZoon which is built on dominator. It’s in fairly early stage development but offers a higher level interface than dominator.

My understanding is you always need a runtime, somethings needs to drive the async flow. But there are others on the market, just not without the.. market domination... of tokio.

https://github.com/smol-rs/smol looks promising simply for being minimal

https://github.com/bytedance/monoio looks potentially easier to work with than tokio

https://github.com/DataDog/glommio is built around linux io_uring and seems somewhat promising for performance reasons.

I haven't played with any of these yet, because Tokio is unfortunately the path of least resistance. And a bit viral in how it's infected tings.

There is also https://github.com/smol-rs/smol which has components which you can compose into your own executor if you still need async IO but your usage patterns don't fit into the general purpose ones that Tokio provides.

If you need precise control over scheduling, consider building something on top of https://github.com/smol-rs/smol

Tokio is a "take what you need" framework, whilst Async-std started as an "everything the box" solution. Today both have a lot of crossover with micro async runtimes like smol becoming the foundation one of framework and optionally usable in the other. The ability to rip out a small dependent sub-crate (dependent package) like smol and use it independently with ease never get's boring, by the way. It's great way to include a test runtime in an async library without forcing the inclusion of a giant async framework.

Helix uses tokio. smol might be a good alternative however.

No, still active on GitHub. What gave you that idea? https://github.com/smol-rs/smol

Found the issue in Google cache. I'm not sure it's really fair of me to post this link here, but equally I think it's better to give the actual text rather than leave it vague.

https://webcache.googleusercontent.com/search?q=cache:PRjMyv...