Fil-C: Garbage In, Memory Safety Out [video]

A bold claim about making old-school code safer sparked instant side-eye and running jokes

TLDR: A new talk argues that C code can be made much safer without abandoning the language, a big deal because C is everywhere and security flaws can be serious. But the comment section turned into a trust battle, with skeptics saying the safety claims may be more marketing than miracle.

A new talk from Filip Pizlo comes in swinging with a very big promise: maybe the old programming language C doesn’t have to be the dangerous wild west everyone says it is. In plain English, that matters because C powers huge chunks of software, and security bugs in it can be disastrous. But on Hacker News, the crowd wasn’t exactly throwing roses — they were reaching for the fact-check button.

The loudest reaction was basically: “Hold on, that doesn’t add up.” One commenter, wasmperson, accused the talk of playing a shell game, saying the project calls things “safe” only because a custom library is standing in front of the usual risky parts. Translation for non-experts: critics think the danger may not be gone, just hidden behind a curtain. That instantly set off the classic internet showdown: bold inventor energy versus skeptical engineer energy.

Then came the meta-drama. A commenter joked they were “overdue for a Fil-C post,” and moderator dang basically rolled out a whole greatest-hits list of past Fil-C debates, which gave the thread a deliciously exhausted vibe: not this again, but also absolutely this again. And for pure comedy, tialaramex resurfaced an older joke about a computer memory address containing the word “LAUGHING,” turning a serious safety debate into a nerdy meme. So yes, the talk is about memory safety — but the real spectacle is the community asking whether this is a breakthrough, a loophole, or just the latest episode in an ongoing tech soap opera.

Key Points

  • The article content is a video listing for a 52-minute talk titled "Fil-C: Garbage In, Memory Safety Out!" by Filip Pizlo.
  • The talk’s abstract states that C and C++ are widely regarded as not being memory-safe programming languages.
  • The abstract says a simple bug in one part of a C program can enable remote code execution despite sophisticated mitigations.
  • The article says the severity of memory-safety issues has pushed programmers to consider rewriting code from C and C++ into safer languages.
  • The talk is described as challenging the conventional wisdom around C and C++ memory safety.

Hottest takes

"all syscalls are safe because they're implemented by his custom libc" — wasmperson
"we were overdue for a Fil-C post on HN" — LugosFergus
"I’ll do it CPS style" — dang
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.