Using memory unsafe languages when practical alternatives exist

[zmanion]

A bad practice: Using memory unsafe languages (e.g., C, C++) when practical alternatives exist. "Practical" includes but is not limited to:

• Technically functional for performance, memory/storage limitations, portability, platform
• Economically practical, cost to swith development platform, cost to create new software, cost to rewrite existing software

Memory safe languages (e.g., Java, Rust, Go) remove certain classes of vulnerabilities (like buffer overflows) but are not immune to all vulnerabilities (e.g., logic bugs, deserialization).