The state of building user interfaces in Rust
areweguiyet.com
The state of building user interfaces in Rust
1–10 of 156 posts
Re: The state of building user interfaces in Rust
#2Uhhh.. for a page thats about GUIs, this seems awfully sparse for the actual look and feel of said GUIs.
How about some screenshots?
Its very difficult to compare X to Y anywhere on this site. Its just an aggregator, not really an exemplary resource.
Re: The state of building user interfaces in Rust
#3Uhhh.. for a page thats about GUIs, this seems awfully sparse for the actual look and feel of said GUIs. How about some screenshots? Its very difficult to compare X to Y anywhere on this site. Its just an aggregator, not really an exemplary resource.
The answer to the question posed in the site's domain name is "no", unfortunately.
It looks like it just grabbed the intro to each project's self-description, but blurbs like "Zero-cost ultra-high-performance declarative DOM library using FRP signals" would be worth very little even with screenshots.
Re: The state of building user interfaces in Rust
#4Uhhh.. for a page thats about GUIs, this seems awfully sparse for the actual look and feel of said GUIs. How about some screenshots? Its very difficult to compare X to Y anywhere on this site. Its just an aggregator, not really an exemplary resource.
Perhaps it's to show how fragmented the community is.
Re: The state of building user interfaces in Rust
#5Uhhh.. for a page thats about GUIs, this seems awfully sparse for the actual look and feel of said GUIs. How about some screenshots? Its very difficult to compare X to Y anywhere on this site. Its just an aggregator, not really an exemplary resource.
Is that actually needed? Styling is largely a user decision. They might have defaults yes, but if you looked at a raw HTML page with no CSS styling, you might come to the conclusion that websites have an ugly GUI...
Re: The state of building user interfaces in Rust
#6Uhhh.. for a page thats about GUIs, this seems awfully sparse for the actual look and feel of said GUIs. How about some screenshots? Its very difficult to compare X to Y anywhere on this site. Its just an aggregator, not really an exemplary resource.
Yes, I think it's trying to be comprehensive (as far as possible) rather than detailed. Given the amount of frameworks listed, including representative screenshots or comparisons for each would be a substantial effort.
The best primer on the current(ish) state of GUI programming in Rust, IMO, is this article from 2025 which is linked on that page: https://www.boringcactus.com/2025/04/13/2025-survey-of-rust-...
Re: The state of building user interfaces in Rust
#7Uhhh.. for a page thats about GUIs, this seems awfully sparse for the actual look and feel of said GUIs. How about some screenshots? Its very difficult to compare X to Y anywhere on this site. Its just an aggregator, not really an exemplary resource.
Is that actually needed? Styling is largely a user decision. They might have defaults yes, but if you looked at a raw HTML page with no CSS styling, you might come to the conclusion that websites have an ugly GUI...
This is the mindset that gives you Java-Style GUIs.
Re: The state of building user interfaces in Rust
#8qmetaobject-rs gives you the best of both worlds: logic in rust, UI in arguably world's best cross platform framework Qt.
Re: The state of building user interfaces in Rust
#9Uhhh.. for a page thats about GUIs, this seems awfully sparse for the actual look and feel of said GUIs. How about some screenshots? Its very difficult to compare X to Y anywhere on this site. Its just an aggregator, not really an exemplary resource.
Is that actually needed? Styling is largely a user decision. They might have defaults yes, but if you looked at a raw HTML page with no CSS styling, you might come to the conclusion that websites have an ugly GUI...
It absolutely is. Defaults matter, most developers just want a GUI for their app that doesn't look like ass. Almost no one wants to mess with styling.
Re: The state of building user interfaces in Rust
#10Earlier quoted context omitted.
Is that actually needed? Styling is largely a user decision. They might have defaults yes, but if you looked at a raw HTML page with no CSS styling, you might come to the conclusion that websites have an ugly GUI...
It absolutely is. Defaults matter, most developers just want a GUI for their app that doesn't look like ass. Almost no one wants to mess with styling.
That's why developers have UI/UX and design experts assigned to them. That's why Figma exists. CSS was an attempt to not have to deal with styling. It failed, and landed in the other direction.