3 ms·
If I ommited that first part of the sentence the points made afterwards would remain the same. I did so to indicate that it's not the first time the Rust commun
by ghostwriter 6y ago
If I ommited that first part of the sentence the points made afterwards would remain the same. I did so to indicate that it's not the first time the Rust community suggests that something should be (re-)written in Rust for memory-safety reasons, in a project that has a well-established C-codebase. I'd argue it's the same "Just install Linux" situation that you mention, and that "Linux" may not be the answer.
- pvg 6y agoit's not the first time the Rust community suggests that something should be (re-)written in Rust The article is not about that, though, it's specifically about the various issues surrounding the use of Rust for Linux kernel development.
- Ar-Curunir 6y agoThe Rust community is not advocating that, it’s kernel developers that are interested in writing new components in Rust. So no proposal of rewriting by any Rust developers
- geofft 6y agoAnd 'ghostwriter stated elsewhere in this thread that the previous round of these comments was in reply to an article talking about how QEMU should start to develop new device backends as out-of-process Rust programs - which also was not about outsiders proposing a complete rewrite, either. https://news.ycombinator.com/item?id=24133292 https://news.ycombinator.com/item?id=24133292 http://blog.vmsplice.net/2020/08/why-qemu-should-move-from-c-to-rust.html http://blog.vmsplice.net/2020/08/why-qemu-should-move-from-c... Perhaps the most long-lasting harm of the Rust Evangelism Strike Force has been the rise of the Anything But Rust Counterinsurgency, who sees that someone, somewhere, is thinking about Rust, and needs to convince them that they're making a mistake.