this post was submitted on 26 Feb 2024
267 points (96.5% liked)
Programming
17432 readers
213 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 [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Please show me a single "good" programmer who is working with C/C++ and hasn't had a single memory bugs in a decade.
Check out Eskil Steenberg. He's mostly a game dev, but he has some really good talks.
And you know with 100% certainty he hasn't had a single memory bug in his last decade of developing?
He has written his own libraries and programs to ensure these things don't happen.
What you people need to understand is that these problems have been solved before Rust. They just weren't baked into the language. And so people made mistakes.
https://www.youtube.com/watch?v=pvkn9Xz-xks
I'm not saying Rust is not always the better choice. Of course not. I'm just oh-so-weary of this rewrite-the-world zealotry a lot of people have about it.
You mean grown-ups?
No, children.
People who are about memory safety are children? Bruh.
That is very much not what I said, bruh.