&gt;  New Rust code will have undiscovered issues too, even if they&#x27;re not memory or stack related.<p>Memory issues have a tendency to be the most severe types of issues from a security perspective. (Not always, but with a high frequency.) Other issues that may occur with a rewrite may be security problems as well, but the security track records of network-facing software written in old-timey C speak for themselves: memory safety issues make up a huge fraction of their vulnerabilities.<p>&gt; I feel that this effort might be better spent fixing and finding problems with glibc---and continuing the development of tools to find those problems, to benefit _all_ of our old C libraries and programs---than rewriting for the sake of rewriting.<p>So we&#x27;ve been trying that for the past 35 years since C was released in 1978, and we&#x27;ve completely failed to move beyond making the same basic memory management errors again and again and again. I think that if we couldn&#x27;t do it in 35 years, we aren&#x27;t likely to be able to by just trying a little harder this one time.