July 25, 2026
Pointer sisters are fighting
Memory Safety Absolutists
Safer software fight turns into a messy loyalty war in the comments
TLDR: A new tool called Fil-C could make older software much safer, but instead of calm applause, the community launched into a loyalty war over whether Rust, Fil-C, or something else deserves the “safest” crown. Readers agree safety matters because bugs hit real users, but they’re split on whether crashes are good enough or prevention is the only win.
The original post tries to make one thing clear: this isn’t just another Rust fan club vs. everyone else showdown. It’s about a new tool called Fil-C, which promises to make older software written in C and C++ much safer by turning dangerous memory mistakes into crashes instead of silent security disasters. Sounds nice, right? Well, the comments instantly turned it into a full-on ideology brawl over who really cares about safety.
The most emotional reaction came from regular-user panic, not programmer pride. One commenter basically said, I don’t want to care about coding tribes, I just don’t want some random app to get hacked because of a bug in a file player. That set the tone: for many readers, this isn’t an abstract nerd argument, it’s “please stop shipping stuff that can explode on my computer.” But then the knives came out. One side argued that Fil-C only makes broken programs fail loudly, while Rust tries to stop those mistakes before the program is even released. Another commenter accused Fil-C creator rhetoric of being pure attention-maxing anti-Rust bait, saying people with old grudges are gleefully piling on just to give Rust fans “a taste of their own medicine.” Ouch.
There was also classic comment-section one-upmanship: if Fil-C is really just a new runtime layer, why not let other languages use it too? And for the true connoisseurs of chaos, someone casually tossed in “have you tried modal type systems?” — the kind of hyper-nerdy flex that makes these threads feel like a food fight at a graduate seminar. The vibe overall: everyone says they want safer software, but they absolutely cannot agree on whose banner gets the credit.
Key Points
- •The article contrasts Rust’s compile-time memory-safety model with C, C++ and Zig, which generally leave memory safety to programmers.
- •Fil-C is presented as a runtime approach for C and C++ that traps invalid memory accesses such as out-of-bounds access and use-after-free.
- •According to the article, Fil-C achieves this through garbage collection and InvisiCaps, and Zig may gain a similar compilation mode inspired by it.
- •The article cites criticism from Fil-C author Filip Pizlo and wording from Andrew Kelley that characterize Rust as not truly memory safe because of `unsafe`.
- •The author argues Fil-C is not a zero-cost drop-in replacement, citing ABI incompatibility, potential multi-times slowdowns, and the introduction of garbage collection.