3 ms·
This is the primary roadblock to Rust deployment IMHO. It's really hard to get over the hump at the start. You do all of the trivial examples in the manual ju
by jandrese 7y ago
This is the primary roadblock to Rust deployment IMHO. It's really hard to get over the hump at the start. You do all of the trivial examples in the manual just fine, but immediately run into issues when you write your own code.
- pjmlp 7y agoSpecially if one tries to do a GUI or game as the first step after going through the book.
- renox 7y agoThe GUI is an issue for all the non-platform languages.. It took a lot of effort for Java with average results. Python's Qt wrappers seems to be more successful.
- pjmlp 7y agoOn Rust it goes beyond that, because borrow checker semantics still aren't productive in typical GUI programming patterns, like self referencial structs from event handlers, leading to Rc<RefCell<>> and clone() calls everywhere. Not saying that it won't improve, just stating the current state. Even with reactive UIs as way to get around those callbacks, relm isn't as easy as Fabulous, SwiftUI, Elm, with the caveat that reactive UIs are heavier on the memory allocator.