The Problem with C++ Safety: Modern C++ Is a Mindset, Not a Standard
1 comments · c++
- Comments7
1 comments · c++
Story details from Lobsters ↗ · linked article on modernescpp.com.
The Problem with C++ Safety: Modern C++ Is a Mindset, Not a Standard was first seen on Lobsters · Hottest on Nov 2, 2026. Since then it has appeared in 22 checks on 1 different day. Its best position was #14 of 25, reached on Nov 2, 10:51 UTC. It dropped off the list after Nov 2, 15:21 UTC.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
"Modern C++" is a meme at this point. When C++11 came out, everyone talked about modern C++. Back then, it was justified - move semantics were a real and significant innovation. But here we are, one and a half decades later, still talking about "modern C++". Nobody can tell me what "modern C++" is anymore. Is it…
You are right but moreover. We have tried better education for 30years. Guess what? The problem is still there. At some point it is time to wonder why this magical solution we keep using does not produce good outcomes! Meanwhile, in Rust, we got an actual factual use case at large scale, in real industry settings…
> Those with experience should correct me if I’m wrong, but talking to the C++ devs in my life tells me that there’s a long memory of being bitten by innocent-looking standard library constructs, both in safety and the performance that a lot of C++ projects call for. Yep. In fact, the form of `std::equal` used in…
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 2, 15:21 UTC, after 1 day of trending.
#14 on Lobsters · Hottest, on Nov 2, 10:51 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 2, 2026 and has been on the list on 1 day (22 checks) since.