Really? We did not need Rust? Here is what some of the best paid C++ Developers in the world come up with after billions of dollars invested in product development:
You do realize Chrome's code has a lineage that is over 24 year old, based on khtml.
If you are starting a project from scratch with C++, you can avoid a lot of the pitfalls chrome's team has. Additionally Google has an arguably poor C++ coding style that is also completely out of date.
A company that uses C++ more effectively is arguably Adobe, who has the great Sean Parent.
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.
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.
If you are starting a project from scratch with C++, you can avoid a lot of the pitfalls chrome's team has. Additionally Google has an arguably poor C++ coding style that is also completely out of date.
A company that uses C++ more effectively is arguably Adobe, who has the great Sean Parent.