- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Very interesting and understandable explanations of low level architecture and filesystems, namespaces, userspace, kernel functions, drivers etc.
Highly recommend!
Very interesting and understandable explanations of low level architecture and filesystems, namespaces, userspace, kernel functions, drivers etc.
Highly recommend!
Yes, it’s called “not being a shit programmer.”
Ahah, I’m pretty sure many of the programmers on Linux et al, that worked on code with CVEs are still better programmers than you will ever be. The fact is that a lot of projects are just complex and they are hard to reason about on languages like C.
But I guess you know that. Keep trolling.
ALL CODE CAN HAVE BUGS BECAUSE WE ARE ALL HUMAN. NO ONE IS DENYING THAT.
But thinking that Rust is inherently safer is actually trolling. I don’t care what you’re doing or who you are, you can make a gigantic security hole in ANY language, including Rust, and there’s zero difference. If you really think people are going around screwing up in C more than people are screwing up in Rust, particularly because they feel like “RUST IS SAFER I CAN DO ANYTHING”, you’re delusional.
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
Sick of debating you people on this. You can’t understand basic logic which tells me right away that you’re either not a programmer or a really bad one, or, more likely, you have some sort of investment in the language’s success.
There’s no conflict in the statements that you need to be a good C programmer and that it’s impossible to be a perfect programmer. This non-argument is you either not understanding common sense and logic, or you grasping at straws in the vain hope that people will think you’re right because you’re so obsessed with your language of the year that will be forgotten soon enough and replaced with, again, C and other traditional, good, useful languages.
I don’t know which is the case, but the frenzied, unhinged way you’re trying to defend rust makes me think you have an investment in the language in some way, which makes your argument invalid. I have no such attachments.
If you can’t understand such common sense arguments, I can’t believe that you even know how to write “Hello World” in any language.
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