Oh look at the time, it's C and C++ bashing again. Uh people, the biggest memory unsafeness pitfalls in C++ are perfectly avoidable if you just use a modern style of C++ and follow a few simple, machine checkable, rules. In particular if you get in the habit of treating the new and delete keywords as red flags (replacements make_unique / make_shared and destruction at end of scope) it becomes really easy to not have dangling pointers.