The issue isn’t that patching and fixing code to be safe takes a ton of your own time, but it’s about the risk to everyone using your code. From security risks

The issue isn’t that patching and fixing code to be safe takes a ton of your own time, but it’s about the risk to everyone using your code. From security risks to simple crashes, C++’s unsafe nature has caused a lot of issues in production in my experience. From renders and apps that crash to subtle security bugs. Not having to focus on those when shipping software to customers means I can focus more on the actual logic and the associated bugs instead. I’m not getting back crash reports and CVEs that sucks up my time. My users in turn aren’t getting affected by my crashes and security issues. Every person who reviews my code can also understand the language guarantees and stop passing my code through that lens and instead focus their mental energy on the other aspects of my code, like catching logic bugs. The effects of a memory safe language extend very far