News for hackers. Stuff that matters.
Re:Why Rust Isn't Killing C++ by smitty1e on Thursday May 02, 2024 @09:11PM (#40243023)
Prediction: in five years or so, gcc shall have gained some extensions which, combined with some ludicrous boost.org template gymnastics, manage to duplicate Rust's borrow checker.

C++ will then kick back, light up a cigarette, take a long drag, exhale a cloud, and wonder aloud what the next "killer feature" will be.

Re:Why Rust Isn't Killing C++ by Expurple on Friday May 03, 2024 @01:25AM (#40244355)
Good luck making all your teammates use these boost templates and use them correctly. And debugging these layers of templates.

A classic from the old Rust FAQ:

>> I already write perfect C++. What does Rust give me?

> Modern C++ includes many features that make writing safe and correct code less error-prone, but it’s not perfect, and it’s still easy to introduce unsafety. This is something the C++ core developers are working to overcome, but C++ is limited by a long history that predates a lot of the ideas they are now trying to implement.

> Rust was designed from day one to be a safe systems programming language, which means it’s not limited by historic design decisions that make getting safety right in C++ so complicated. In C++, safety is achieved by careful personal discipline, and is very easy to get wrong. In Rust, safety is the default. It gives you the ability to work in a team that includes people less perfect than you are, without having to spend your time double-checking their code for safety bugs.

Re:Why Rust Isn't Killing C++ by smitty1e on Friday May 03, 2024 @04:45AM (#40245525)
There is no luck; there is only Freewill interacting with the Borrow Checker of Destiny.