&gt; Languages come and go but C++ remains.<p>And those other languages have slowly eroded C++&#x27;s dominance. You have to remember that in the early &#x27;90s, C and C++ had nearly 100% market share for all applications. That dwindled with the rise of Java, then dwindled more with the rise of dynamic languages, and the mobile&#x2F;modern era made it dwindle even more with Objective-C, Swift, and Go. Now C++ is a popular language for a <i>certain class of applications</i>, but by and large new programmers aren&#x27;t even learning it anymore. That&#x27;s a huge shift.<p>&gt; In the meantime C++ has evolved. I cant remember the last time I had an uninitialized memory, null pointers, or buffer overflow -bug.<p>I do. <a href="https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;buglist.cgi?query_format=specific&amp;order=relevance+desc&amp;bug_status=__all__&amp;product=&amp;content=uaf&amp;comments=0" rel="nofollow">https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;buglist.cgi?query_format=specif...</a><p>&gt; And finally there is &quot;C++ Core Guidelines&quot; which aims to be checkable by tools. So you get a warning when you are relying on undefined behaviour.<p>As I&#x27;ve said before, I have questions about this tool: how much like C++ it will really be after ruling out so much code, and how they plan to statically guarantee noalias on function boundaries in the presence of shared_ptr.