Every single C/C++ project without exception should consider rewriting their project in Rust, or at least introducing Rust code to the project gradually with the aim of eventually replacing all C/C++ code. This includes the linux kernel, the nix package manger, and any other C/C++ project named in that article. (Of course, there are good reasons why such a rewrite might not be tractable for any given software project, but the possibility should at least be on the maintainers’ radar).
This isn’t so much because Rust is a good language, but because C and C++ are poor ones. C is a 50 year old programming language written and standardized before the programming profession had come to learn a lot about what make a programming language nice to program in (and subject to what sort of compiler you could write easily on a 1970s computer). C++ is a bunch of kludges on top of C that are difficult for any one person to fully understand. More importantly, these languages make it very easy to write code with memory safety bugs, and using software with memory safety bugs no one knows about leads to security vulnerabilities that affect the people running that software. If it were possible I would love to not execute a single line of code on my computer compiled from C source, but that is not practical right now.
I’m not sure if you’ve read TFA or not, but it specifically calls out the behavior by non-contributors to request projects undergo a “Rewrite it in Rust”, and how it can be both amusing and problematic.