this post was submitted on 09 Jun 2023
105 points (100.0% liked)
Linux
1259 readers
82 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Skeptical. Writing a graphical UI toolkit is a freight train of work. I'm positively curious about anything that's not GTK but I'm not sure going with a new toolkit is the right decision. Qt is the mature kid on the block that's been proven in more environments than I can count. Moreover it's a complete application framework with a ton of convenience libraries needed for speedy development already included. I guess those can be supplanted in the form of separate Rust libs. Personally I'd have gone with Qt for such a project but I'd be happy to be proven wrong.
This is coming from personal experience/opinion, but after trying to create a simple app in GTK4 Rust bindings I was so confused because of how alien the programming style was compared to typical Rust programming. After trying Iced it was much simpler and made so much more sense, no silly decorators or anything, you can define the view and the update loop separately, and interactions are handled by messages using pattern matching. The inheritance based OOP doesn't work well with Rust, and Iced has none of it, because it was made for Rust specifically.
I'm guessing QT bindings are similarly in a different style of programming and can't imagine that meshing well with native Rust code. Iced has a lot of merits to it and having the opportunity to both help it develop and use a native Rust framework in a Rust project makes a lot of sense.