Hacker News Reader

A new language will eventually acquire its own grungy legacy just like C++ did, unless that new language aggressively breaks backward compatibility.

I think the best practice is for people to stick to a subset of safe patterns in mature languages. For C++, that's probably the C++ Core Guidelines:

https://isocpp.github.io/CppCoreGuidelines/

View on HN

C++ was grungy in the 90’s, and, well, Rust as it is now is better than C++ as it is now, the comparison that matters now. Rust in 30 years will be better than C++ in 30 years. And safety is a big deal feature, and Rust has it. If it doesn’t have future big deal features, future languages can have it.

I reject the notion that C++‘s “maturity” is a substantial advantage given its unsafety.

Reply on news.ycombinator.com