• 3 Posts
  • 52 Comments
Joined 11 months ago
cake
Cake day: August 14th, 2023

help-circle
rss












  • You keep coming up with insults or inflamatory comments instead of answering the points, when I’m just trying to have a discussion of ideas. I don’t understand why I am being unhinged when I even agreed with you partially.

    I’m not a Rust programmer, I just play occasionally with it on pet projects. The languages I’m most experienced in are C++ and then C, I have no “horse in the race” of Rust, and I don’t see c/c++ going away anytime soon, I just see what the language improves on them


  • You are not very consistent, first you imply that not “being a shitty programmer” is the fix for security issues in C. And then you say that any programmer can and will make mistakes…

    Again you refuse to see my argument: yes I agree that viewing Rust, or any other language, as being a panaceia is wrong and following the hype. But Rust is provably better than C w.r.t to memory safety issues because it, provably, finds memory issues during compile time. I’m not discussing other types of security issues.

    Yes C needs all that “freedom” with memory due to its low level use cases, but Rust is proving that it can also cover those cases (with the unsafe keyword) and cover the opposite cases where you want more strict memory usage and safety, so much so that you see now operating systems and firmware being developed in it. I won’t argue and compare performance as I don’t know enough.

    You could argue that Rust by providing the “unsafe”, keyword can and will have memory issues, but IMO the fact that you need to enclose unsafe operations in a scope allows for more focused reviewing and auditing