asynchron VS redux-rs

if you don't want to block your busy event loop or want to avoid livelock, deadpool (whatever), reduce use case of channels, threadpool or so. just take a look: https://github.com/Ar37-rs/asynchron it's quite handy, no unsafe, no dependecies. there's an example how to mix it with async (tokio, reqwest). but if you are afraid to use async http client you can use "ureq" crate.

maybe you can check this, if it fit your need: https://github.com/Ar37-rs/asynchron/tree/main/example/fltk_fetch only tested on multithreaded environment so far.

try this, sync/async friendly: https://github.com/Ar37-rs/asynchron there's an example under example/fltk_fetch folder

I put together a fairly simple, Redux-like state container, inspired by redux-rs but with the ability to generate async Streams instead of using callbacks. (Ultimately the goal here is web frontend/GUI development that can use the Elm-ish model without any kind of VDOM, by targeting updates to particular UI elements when a stream gives a new value.)

Just wondering if anyone has experience with some of the state management libraries out there now for rust. For example, state, reactive-state, redux-rs, or stores to name a few. I come from a React background, and I'm currently building a GUI app in Rust with FLTK-RS. I've already built out a good bit of my app using rusts built in RefCell pattern to mutate my app state, but I'm interested in a more "reactive" approach. Think these crates could have something to offer over RefCell or Arc?