To be fair/devil's advocate - "GUI" has been phonetically pronounced as "Gooey" by many people since inception, thus I think it is entirely reasonable for them to have adopted this name entirely unaware of the eponymous python library.
I'm a bit sad to say that some of the Rust GUI frameworks have lost me soley due to their awful text rendering. I shot up in my seat when I saw the login form demo. It actually looked good!
I'm also a huge fan of the reactive model. It feels very natural for developing UIs. The best implementation I've seen of reactivity in Rust is in the Dominator web framework (well, the author calls it a DOM library, but I believe framework is more appropriate). In case it piques your interest, Dominator's reactive primitives are available separately in the [futures-signals](https://docs.rs/futures-signals/latest/futures_signals/index...) crate.
8 comments
[ 3.0 ms ] story [ 30.2 ms ] threadhttps://github.com/chriskiehl/Gooey
https://news.ycombinator.com/item?id=38586767 (120 comments)
On the reactivity front it would be interesting to compare how is different in principle and in performance vs some other frameworks
I'm a bit sad to say that some of the Rust GUI frameworks have lost me soley due to their awful text rendering. I shot up in my seat when I saw the login form demo. It actually looked good!
I'm also a huge fan of the reactive model. It feels very natural for developing UIs. The best implementation I've seen of reactivity in Rust is in the Dominator web framework (well, the author calls it a DOM library, but I believe framework is more appropriate). In case it piques your interest, Dominator's reactive primitives are available separately in the [futures-signals](https://docs.rs/futures-signals/latest/futures_signals/index...) crate.
I can't wait to give this framework a try!