I know many people fear about this article, but here's what you got.
For decades, memory safety flaws have fueled countless security incidents across the industry, undermining trust in technology and causing billions in losses. Traditional measures—such as code audits, fuzzing, and exploit mitigations—have helped but fallen short of stopping the problem, all while driving up costs.
Promising advances in hardware are emerging. Features such as ARM’s Memory Tagging Extension (MTE) which is equipped since Google Pixel-8 and the Capability Hardware Enhanced RISC Instructions (CHERI) architecture provide valuable, complementary defenses—especially for securing existing code.
For decades, memory safety flaws have fueled countless security incidents across the industry, undermining trust in technology and causing billions in losses. Traditional measures—such as code audits, fuzzing, and exploit mitigations—have helped but fallen short of stopping the problem, all while driving up costs.
Promising advances in hardware are emerging. Features such as ARM’s Memory Tagging Extension (MTE) which is equipped since Google Pixel-8 and the Capability Hardware Enhanced RISC Instructions (CHERI) architecture provide valuable, complementary defenses—especially for securing existing code.
https://www.gizvault.com/archives/what-is-fil-c-and-how-to-use-it
I don't fxxking care if you are stupid enough to make this post dead, but it's great appreciated to whom developed "dead" rather than disappear in HN.