5 ms·
All GUI domain seems to be one big state, and that is the kind of place Rust refuses to interact with easily.
by RealityVoid 2y ago
All GUI domain seems to be one big state, and that is the kind of place Rust refuses to interact with easily.
- jenadine 2y agoThat's not true. There are many GUI libraries for Rust.
- RealityVoid 2y agoThere are. You can do it. It's just that the language fights you on it.
- bfrog 2y agoNot really, there’s two models that work. The react model and the immediate model. The whole class inherits widget hellscape is not, no loss there. That route inevitably leads to bugs that are hard to find and fix because of all the weird state buried in inherited types.
- ericwood 2y agoGlobal mutable state is difficult to handle correctly and Rust forces you to think through the consequences. There's no shortage of patterns for safely working with it, but you can't take the easy (and unsafe!) way out.
- tonyarkles 2y agoSort of. Last time I looked, about a year ago, there were a bunch and all of the ones I looked at/tried seemed really awkward to use. I don’t love Qt either, but in C++ land it’s a pretty reliable way to slap together a simple UI that doesn’t require a whole lot of ceremony.
- feverzsj 2y agoThey are just far far from mature. Your best bet for rust gui is still Qt bindings.
- galangalalgol 2y agoI really like egui. People talk about it not being professional because it is raster graphics and doesn't have native widgets, but neither of those things are anywhere on my customer's priority list.
- timeon 2y agoTime will tell if Rust GUI libraries will be able to mature but maturity is different topic.
- jenadine 2y agoWhat about Slint? It is stable and used by real software.