Both are problems with siding, one is far more serious than the other. I'm not a fan of Java, but cpp people being disingenuous is a pet peeve. "Modern" cpp still sucks, it just sucks less - it's not useful to pretend otherwise.
Our cloud service at Sococo, back in the day, their principle bug-tracing activity was Java null pointers. The second? leaks. Both problems with pointer management.
However you slice it, it takes discipline to get memory allocation right. No magic bullet.
But they do lead to service downtime, loss of opportunity, broken contracts.
Not really the same, but important as well.
Completely unrelated: there are at least two dedicated anti c++ communities.
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++”.
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?