Uh, using Adobe as an argument in favour of C++ as a reliable programming language from a memory safety perspective is not a good argument. Just looking at the CVE count tells a story that cuts across their entire product line, and then we have the long and storied history of Flash and Acrobat vulnerabilities.

Any non-trivial code base in any language will have security issues, but the argument that these security vulnerabilities are a result of using C++ poorly doesn't change the fact that C and C++ have tons of footguns and pitfalls based on both modern and legacy code.

Adobe as in Acrobat Reader?

https://www.cvedetails.com/vulnerability-list/vendor_id-53/p...

or Adobe as in Photoshop?

https://www.cvedetails.com/vulnerability-list/vendor_id-53/p...

Can you elaborate on the code style? So many put google c++ code style on a pedestal and force it on everyone as if it is divine.

That's the problem with these languages (both C and C++) — it's always the user's fault. The language blows up if you accidentally miss one of the twelve thousand rules? User's fault, PEBCAK. If only the poster X was writing the software in question, these bugs never would have happened. I've seen this argument a million times.

With great power comes great responsibility. :)