Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparison to vgtk #274

Open
Gaelan opened this issue Mar 6, 2021 · 1 comment
Open

Comparison to vgtk #274

Gaelan opened this issue Mar 6, 2021 · 1 comment

Comments

@Gaelan
Copy link

Gaelan commented Mar 6, 2021

This crate and vgtk seem pretty similar on a first glance—they're both GUI libraries with a "modern" Elm/React-style API. It'd be nice if there was some documentation somewhere describing the differences and pros/cons of each.

Some preliminary notes from a quick look at each crate:

  • vgtk uses an HTML-like syntax for defining UIs, while relm's syntax looks more like normal Rust. (Both syntaxes are implemented as macros usable from within normal Rust files.)
  • vgtk uses Futures, while relm doesn't.
  • vgtk uses a Virtual DOM-style approach, while relm works by inserting code to update the UI after state updates at compile time. The tradeoff here seems to be that relm's approach is more efficient, but vgtk's has fewer gotchas.
  • relm is more popular and more actively maintained.
@Gaelan
Copy link
Author

Gaelan commented Mar 6, 2021

I've opened an equivalent issue on vgtk here: bodil/vgtk#78

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant