Statistics commonly reported about the amount of memory safety problems in comparison to all reported security problems. Microsoft and Google in particular report this exact number.
Industry analysis has shown in some cases, that despite rigorous code reviews as well as other preventive and detective controls, up to 70 percent of security vulnerabilities in memory unsafe languages patched and assigned a CVE designation are due to memory safety issues.Back to the Building Blocks: A Path Toward Secure and Measurable Software
Dev A: Damn, another segfault. What happened this time?
Dev B: Sounds like another 70 moment, that's what.
Prevent the 70. Pick memory safety.
No, stupid GC languages don't count, they suck.
lmao. serves you right for using a program written by a 70er.
How about you pull your head out of your ass, learn a language from the 21st century, and kick the 70 to the curb.
You think you're so infallible as a programmer, you're the reason why endless 70 happens. You're a threat to national security.
You think you're so infallible as a programmer, you're the reason why endless 70 happens. You're a threat to national security.
Brought to you by a dumb salty Cnile who doesn't know what's best.