Basically title, with System76 moving from gnome to their new rust built COSMIC environment what are your thoughts?
You must log in or register to comment.
I’m incredibly interested in COSMIC DE! For multiple different reasons, actually.
- Rust - I’m very interested to see how performant/memory-efficient this DE will be compared with other DEs. Also, I wonder how the Iced toolkit will evolve and be adopted in other projects.
- Benefits over GNOME - I’m looking forward to seeing how much out-of-box customizability and features come with COSMIC over GNOME (which I’m currently using).
- Maintainability going forward - Since the DE basically started from scratch and is using a much better language for robust software, I wonder how much easier and faster it would be to maintain the desktop environment. This potential improved maintainability could be huge in overtaking other DEs sometime soon.
How is rust more memory efficient than c or c++?
It’s not, perhaps they meant memory-safe?
The DE might be more memory efficient given the hindsight and freedom a fresh slate brings, but not strictly due to rust.
There’s several things that make Rust more ideal for writing software that makes efficient use of resources than C or C++.
One of these is how cumbersome it is to use tagged unions in C/C++. They’re integrated as a first class citizen in Rust in the form of enums, and both the standard library and all Rust projects as a whole utilize them extensively. An example would be the
Cow<'a, T>type. The compiler also has some clever tricks like zero-sized types which can reduce the size of types which contain them.On the surface, the borrowing and ownership model is useful for guaranteeing memory safety. Yet if you take that a step further, it’s the perfect tool for finely optimizing resource usage with confidence. In comparison, defensive programming practices are the norm in C and C++ because resource management is risky. So applications written in Rust are more likely to be better optimized.
And the GNOME project doesn’t just use C/C++ right? It uses Javascript for developing all sorts of components and Python for scripting/misc utilties. That’s what I meant by more memory-efficient.
Hey, do you have plans to open any communities into Lemmy?
We created https://kbin.social/m/pop_os
I haven’t been able to contact the owner of https://lemmy.ml/c/pop_os
If the author of the community isn’t responding, I believe you can pop a request over at https://lemmy.ml/c/community_requests to have it transferred to you.
I welcome new and innovative DEs. I am tired of how some organizations handle things. I must however, acknowledge that with every additional major DE comes further fragmentation. COSMIC seems to really care and for that reason I am rooting for them. The negative effects, however, are always in the back of my mind.
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.
