3 ms·
For some reason, the comparison is always current rust Vs 20 year old c++. Mentioning that "modern" (12 year old) c++ does not have these problems gets downvote
by harrid 3y ago
For some reason, the comparison is always current rust Vs 20 year old c++. Mentioning that "modern" (12 year old) c++ does not have these problems gets downvoted.
Completely unrelated: there are at least two dedicated anti c++ communities.
- littlestymaar 3y ago> Mentioning that "modern" (12 year old) c++ does not have these problems gets downvoted. Because it's false, that's why. Modern C++ still has many/most of C++ problems. It solves a bunch of them, but far from all. And telling the opposite to newcomers is a lie that's hurting them because they can end up making even more mistakes than the previous generation, since they were told they didn't have to pay attention thanks to “modern C++”.
- tubthumper8 3y ago> Mentioning that "modern" (12 year old) c++ does not have these problems gets downvoted. I'm not a C++ user but I thought that all of these things are still in "modern" C++, that the new editions only add things, not remove? Are there tools that can automatically rewrite existing code to use the "modern" features?
- harrid 3y agoAnd that's a criticism I can take to a degree on behalf of the language. These relics are still in because mistakes are happening in the governing body. However in practice, they don't matter much. Every CPP dev has a little helper running in the background which immediately flags these mistakes and can auto correct them. It's not an issue, just an annoyance.