This was the interesting point for me too; noting that _new_ C/C++ is where most of the bugs are found, and so it's less important to rewrite old code than it i

This was the interesting point for me too; noting that _new_ C/C++ is where most of the bugs are found, and so it's less important to rewrite old code than it is to transition to memory-safe languages for everything new that gets written. Perhaps this is an obvious point, but I found it interesting . This probably also applies to the Linux kernal work in Rust too; if only new device drivers get written in Rust and the core remains C, it could still be a major win for kernel security. > how does the incremental addition of Rust work in practice? Probably a good starting point: https://firefox-source-docs.mozilla.org/writing-rust-code/cpp-interop.html#accessing-rust-code-and-data-from-c https://firefox-source-docs.mozilla.org/writing-rust-code/cp...