[noch]

> UB, memory leaks, memory corruption, implicit conversions,[...] > In C, 100% of the source code is unsafe

Is it perhaps better to focus on context? That is,cost vs benifit wrt context:

- How much safety and what kind and level of safety assurances does the specific application need?

- How much does it cost in development time/friction, application performance, engineering complexity, [insert other relevant cost axes] to achieve the desired level of safety and safety assurances?

[pjmlp]

As proven by the high integrity security standards, if you want to write safety proven code in C, there is no way around something like MISRA-C, Frama-C, alongside certification tooling like the one sold by LDRA.

https://www.ldra.com/

Naturally this is a kind of expenses that 99% of the companies aren't going to spend until it finally becomes a legal liability to have security exploits on the software.