373
Memory is running out, and so are excuses for software bloat
(www.theregister.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Dec 2025
373 points (98.2% liked)
Programming
24312 readers
254 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
Everyone better start learning Rust.
Rust programs can definitely still consume a lot of memory. Not using a garbage collector certainly helps with memory usage, but it's not going to change it from gigabytes to kilobytes. That requires completely rethinking how things are done.
That said I'm very much in favour of everyone learning Rust, as it's a great language - but for other reasons than memory usage :)
True, but memory will be freed in a more timely manner and memory leaks probably won’t happen.
Memory leaks are more than possible in rust. Rust type system prevents things like free being called on an already free resource. It very much also allows not calling free even when nothing references things. It also makes things like arena allocation a fun endeavor compared to other systems languages. It’s not impossible just trickier. Rust isn’t a panacea, you would need something more like idris with its type system to programmatically enforce resources are freed at runtime during the compilation phase. But a fully dependent type system is very much a bleeding edge thing.
.clone() everything!
I do kind of agree in a way though. Rust forces you to think a bit about memory and the language does tend to guide towards good design. But it's not magic and it's easy to write inefficient Rust too. Especially if you just clone everything. But I personally find Rust to be a good mix of low level control that feels sufficiently high level.
Garbage collected languages can be memory efficient too though. Having easily shared references is great!
After you’ve cloned everything you’ll
Arc<Mutex<>>everything.