Exactly this. This is a never ending problem with C/C++ and it's these same memory corruption CVEs appearing all the time. I also cringe at projects that "comp

Exactly this. This is a never ending problem with C/C++ and it's these same memory corruption CVEs appearing all the time. I also cringe at projects that "compile C to WASM" and then believe that it is immediately "memory-safe". (It really is not.) The only exception for C/C++ projects is Fil-C which that is memory-safe. New projects at this point should just consider using Rust instead.