The InfoQ Podcast · Hands-On Engineering Podcasts · October 2026
Swan is explaining a research project that puts memory safety into the chip, so existing C code can be recompiled instead of rewritten. He puts open source C at billions of lines against tens of millions of lines of Rust, and says rewriting it all would take almost impossibly long even with AI help.
…done. But this can't keep going forever. And so at some point, we'll find ourselves in a situation where there'll just be fewer vulnerabilities left to discover. And that should be a happier place for all of us to exist in because we won't be worrying as much about zero days and their exploitation.
Okay. Well, you mentioned Sherry and the fact that both Android and iPhones are looking into adopting this model. Maybe we can allocate a couple of minutes to get more details to our listeners and understand what Sherry actually is. Maybe we inspire other folks to adopt it.
…is, oh, just rewrite it all in Rust. But if you look at the size of the problem, there's something like five and a half billion lines of open source C C and something like 70 million lines of Rust at the moment. And so if we were to plot our course of how long it would take humanity to rewrite all of that C and C into Rust, even with AI assistance, it's almost an impossibly long duration. And we've also seen projects where rewrites in Rust have introduced new logical flaws because, okay, you get memory safety, but it doesn't mean that everything's invulnerable. You still have to think through the other ways that systems can be attacked. The rewrite of some of the core utils into Rust has unfortunately thrown away decades of hardware experience about what can go wrong with applications. You end up with functionally equivalent replacements, but that have some new bugs in them. They might be not memory safety bugs, but they're still potentially security…
Given the points that you had, having it in Android and iOS will have a very wide span, given the OUB-COTUS nature of the mobile phone. It would be to have a magic wand and you should pick another platform that would have it tomorrow. Which one would that be?
So it would be RISC-V. And I say that because RISC-V is still nascent as an instruction set architecture in terms of its adoption. It's still standards-wise, a little bit more malleable than the x86 and the ARM stuff that we've all become accustomed to. And I think having the Cherry instructions in…
Yeah, probably given the open source nature of RISC-V, we'll have maybe hopefully a better blast radius. But fingers crossed that we get closer to having a more memory-safe ecosystem.