The problem with black-and-white thinking is that it's too simplistic to apply to the great majority of real-world problems. Safe C provides an incremental mig

The problem with black-and-white thinking is that it's too simplistic to apply to the great majority of real-world problems. Safe C provides an incremental migration path from unsafe C to safe C. And you don't need to completely rewrite, but instead address the issues flagged, which will often be a lot less work and risk than an actual rewrite in a new language. (This seems obvious to me, but apparently not?)