> 2. Safe programming languages solve the easy problems: memory leaks, use-after-free errors, array overruns, etc. Safe languages provide no help beyond ordinar

> 2. Safe programming languages solve the easy problems: memory leaks, use-after-free errors, array overruns, etc. Safe languages provide no help beyond ordinary C code in solving the rather more difficult problem of computing a correct answer to an SQL statement. Uhm ... If those were project wide "easy problems", then how come vulnerabilities in a project like Chromium are 70% caused by these "easy problems"? I'd say with that category of bugs on board, you cannot mistrust yourself enough and that there is nothing easy about preventing these bugs all the time over the life-time of a project.