4 ms·

Some of us have no desire to learn Rust… well I did, but found the syntax to be awful. If you already know C, C++ or something else, you really need a good reas

Some of us have no desire to learn Rust… well I did, but found the syntax to be awful. If you already know C, C++ or something else, you really need a good reason to learn a new language, especially one with a syntax as messy as the of Rust. That being said, you do have a valid point that file format parsing really could benefit from a language with the safety features of Rust.

bitwize 5y ago
I'd say making buffer overflow and UAF CVEs Just Go Away -- forever -- is a DAMN good reason to switch to Rust. I've found that prior exposure to C is somewhat negatively correlated with willingness to grok Rust. Something in their mind rebels against it, which is why I say that if you're an "old hand" C programmer who feels that the syntax of Rust is too hard, or the borrow checker is obscure, maybe you shouldn't worry about learining Rust because Rust isn't for you -- it's for your replacement. You're John Henry, the borrow checker is the mechanical spike driver, and no matter how hard you work at it all your programming discipline is just no match.
- fivea 5y ago
  > I'd say making buffer overflow and UAF CVEs Just Go Away -- forever -- is a DAMN good reason to switch to Rust. rocket Crate up to 0.4.6 on Rust uri::Formatter use after free https://vuldb.com/?id.172079 https://vuldb.com/?id.172079 If only people stopped with the cargo cult nonsense that leads to this absurd belief that adopting a tool is a silver bullet to fix their sloppy practices.
  - mrich 5y ago
    You know, seeing one of the few existing Rust CVEs, which is a freak case, hard to exploit - makes me directly want to go back to the language family with the majority of the CVEs assigned. The existence of CVE itself arguably is a result of unsafe C/C++.
    - fivea 5y ago
      > You know, seeing one of the few existing Rust CVEs (...) It is a real world CVE of use-after-free on real world Rust code in production. This demonstrates that, unlike claims from fanboys, mindlessly migrating to Rust does not magically make your code safe and immune to vulnerabilities such as use-after-free, and just like with any other language you still need to know what you are doing.
- mrich 5y ago
  I think you are exactly right and it's sad that you are getting downvoted for this. The "bright" side for coders unwilling to learn new things is that there is lots of legacy C code to maintain to last a lifetime. It's still a bit sad since Rust is just lots of fun to work with.

bitwize 5y ago

I'd say making buffer overflow and UAF CVEs Just Go Away -- forever -- is a DAMN good reason to switch to Rust. I've found that prior exposure to C is somewhat negatively correlated with willingness to grok Rust. Something in their mind rebels against it, which is why I say that if you're an "old hand" C programmer who feels that the syntax of Rust is too hard, or the borrow checker is obscure, maybe you shouldn't worry about learining Rust because Rust isn't for you -- it's for your replacement. You're John Henry, the borrow checker is the mechanical spike driver, and no matter how hard you work at it all your programming discipline is just no match.

fivea 5y ago
> I'd say making buffer overflow and UAF CVEs Just Go Away -- forever -- is a DAMN good reason to switch to Rust. rocket Crate up to 0.4.6 on Rust uri::Formatter use after free https://vuldb.com/?id.172079 https://vuldb.com/?id.172079 If only people stopped with the cargo cult nonsense that leads to this absurd belief that adopting a tool is a silver bullet to fix their sloppy practices.
- mrich 5y ago
  You know, seeing one of the few existing Rust CVEs, which is a freak case, hard to exploit - makes me directly want to go back to the language family with the majority of the CVEs assigned. The existence of CVE itself arguably is a result of unsafe C/C++.
  - fivea 5y ago
    > You know, seeing one of the few existing Rust CVEs (...) It is a real world CVE of use-after-free on real world Rust code in production. This demonstrates that, unlike claims from fanboys, mindlessly migrating to Rust does not magically make your code safe and immune to vulnerabilities such as use-after-free, and just like with any other language you still need to know what you are doing.
mrich 5y ago
I think you are exactly right and it's sad that you are getting downvoted for this. The "bright" side for coders unwilling to learn new things is that there is lots of legacy C code to maintain to last a lifetime. It's still a bit sad since Rust is just lots of fun to work with.