Is It Time to Rewrite the Operating System in Rust?

What people said

equalunique · 2019-05 · Recommendation

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]

Read the original HN comment ↗

oconnor663 · 2023-02 · Reference

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 about who does what.

Read the original HN comment ↗

littlestymaar · 2021-01 · Reference

> 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 because they are easy to implement, while his Rust version was using B-trees just because he could. And as a result, his naive first attempt in Rust outperformed his long-optimized C code. [1]: [VIDEO]

Read the original HN comment ↗