It&#x27;s simple:<p>1. Memory safety issues are the cause of a very large number of security vulnerabilities (often most of them for projects written in C or C++, depending on the software).<p>2. Memory safety-related issues have a relatively high probability of being turned into remote code execution, which is one of the most if not the most severe outcomes.<p>3. C and C++ projects have been empirically observed to have orders of magnitude more memory safety problems than projects written in other languages do.<p>4. The additional classes of security vulnerabilities that managed languages tend to foster do not have the combined prevalence and severity of memory safety problems.<p>So, we would be better served in security by moving to memory-safe languages.