2 ms·
I'm not sure if this will change your mind, but in the Rust world, there's a concept of "unsafe" code that can lead to vulnerabilities. The difference here is
by smt88 7y ago
I'm not sure if this will change your mind, but in the Rust world, there's a concept of "unsafe" code that can lead to vulnerabilities.
The difference here is that a code consumer can check a Rust project for unsafe code, whereas a food consumer cannot check for unsafe contaminants.
- phkahler 7y agoIf it's OK to demand a project use only Rust and not unsafe Rust, then it must be OK to bitch at every C or C++ project and demand they rewrite in Rust. If that sounds absurd, that's because it's supposed to.
- smt88 7y agoThat's not really an apples-to-apples comparison. From what I can tell, actix was using unsafe code to improve benchmark performance, not because safe code was extra work. That's fine, but it was misleadingly marketed as more than a toy project, and it shouldn't have been. Further, rewriting a project is very different from just making different coding decisions when maintaining an existing project. I still think the actix critics are showing how irresponsible they are for blindly using a library without researching it well.