Is It Time to Rewrite the Operating System in Rust?

Channel:InfoQ · Length:1:09:17 · Published:2019-02-25 · Views:310687

Watch on YouTube

Summary

Bryan Cantrill's QCon SF 2019 talk asking whether operating systems should be rewritten in Rust. He draws on his systems experience to discuss C, memory safety and Rust's fit for system software.

Why HN recommends it

Cited in debates about Rust versus C as a thoughtful systems programmer's account of falling for Rust.

very deep dive into operating systems, C, and Rust — HN, 2019

C, C++, Rust, Go & systems languages · Operating systems & kernels · Security & hacking

Subtitles (excerpt)

All right, so my question is is it time to rewrite the operating system in rust? Now, I will give you a little bit of a spoiler alert. This is Betteridge's law of headlines that any article that that kind of asks a question, you can reasonably say no to. So, um I but I I you're not going to get a no out of me on this one. You're going to get um a bunch of qualified yeses, but just to give you a spoiler, um it is a question mark, not necessarily an exclamation point for reasons I'll get into. Um but first and I actually I think it's pretty great that I don't even think I'm the first maybe not even the second presentation to have a slide on what even is the operating system. I mean, we're we're in the OS track, operating system's been around a long time, and apparently we don't even know what they are. Um and it's actually harder to define than than you might think. If you think this is easy, by the way, just say like like what is software? Give me a definition of what software is. And I can wrap you around the axle on your definition of software. Cuz I get I I I will pose you this follow-up question, is Euclid's GCD algorithm software? Was Euclid writing software when he wrote the GCD algorithm?

On Hacker News

My introduction to gVisor was the talk by Emma Haruka Iwao at InfoQ NY 2018: [LINK] I learned of the talk because Brian Cantrill referenced it during his very deep dive into operating systems, C, and Rust given later at the some event: [VIDEO] — equalunique, 2019-05
Bryan Cantrill making a similar point: [VIDEO] > I can write C that frees memory properly...that basically doesn't suffer from memory corruption...I can do that, because I'm controlling heaven and earth in my software. It makes it very hard to compose software. Because even if you and I both know how to write memory safe C, it's very hard for us to have an interface boundary where we can agree ab… — oconnor663, 2023-02
> The reason that C programs often don’t perform as well as an equivalent rust program[1] is that it’s so incredibly hard to do anything at all in C (especially something reliable) that one can usually only do the simplest thing possible and this typically means simple data structures, simple algorithms and arrays Brian Cantrill talks[1] about exactly this: in his C version he was using AVL trees… — littlestymaar, 2021-01
Wow, tough crowd! I don't know that I -- or anyone that knows me -- would accuse me of "ever-evolving advocacy", but yes, I did see promise in node.js in 2010[1]. And yes, we at Joyent built systems on node.js -- but we also added unprecedented debuggability and observability along the way.[2]. While my views may not be "ever" evolving, they're also not incapable of it: by 2014, it was clear that… — bcantrill, 2020-09
I only linked that because most people don't know what B is, and I suppose the difference between "innovation meant to fill the space" and "extention" wasn't so important to me. My source for the claim itself is from 14m30s of Brian Cantrill's talk "Is It Time to Rewrite the Opersting System in Rust" [VIDEO] — 1MachineElf, 2020-06

Related videos