&quot;C just adds memory corruption to the set of issues one has to worry about.&quot;<p>That&#x27;s a very casual way to say that C adds an entire class of errors that lets attackers own your machine with the slightest mistake in the most common coding situations. Memory safety is such a huge increase in security over C that it isn&#x27;t even funny that people use C where not necessary. Type-safety plus good type system gets a start on knocking out data and interface errors. Type systems with context, or just Design-by-Contract, can knock out more interface errors.<p>So, a good type system, type safety, and memory safety should be the baseline for reliable or secure systems. C tosses out the whole baseline in exchange for... running a bit faster or lazy programmers?<p>Note: I&#x27;m talking in general rather than building on existing C projects, where using C makes some sense.