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.
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.
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.