"Rust's compiler prevents common bugs" So does skill. No offense to you, but, this trope is getting so tiresome. If you like the language then go ahead and use it. What is it with the rust crowd that they have to come acrosslike people trying to convert your religion at your front door?

you are viewing a single comment's thread
view the rest of the comments

[–] smiletolerantly@awful.systems 101 points 1 day ago (15 children)

if your skill is so great that you would never cause the kinds of bugs the rust compiler is designed to prevent, then it will never keep you from compiling, and therefore your complaint is unnecessary and you can happily use rust
if you do encounter these error messages, then you are apparently not skilled enough to not use rust, and should use rust

In summary: use rust.

[–] F04118F@feddit.nl 32 points 1 day ago (3 children)

I don't agree with /u/red-crayon-scribbles ' approach to memory safety, but what you're saying isn't entirely true either.

It is possible to manipulate memory in ways that do not conform to Rust's lifecycle/ownership model. In theory, this can even be done correctly.

The problem is that in practice, this leads to the following, many of which were committed by some of the most highly skilled C developers alive, including major kernel contributors:

https://xeiaso.net/blog/series/no-way-to-prevent-this/

[–] Midnitte@beehaw.org 15 points 1 day ago

...echoing statements expressed by hundreds of thousands of programmers who use the only language where 90% of the world's memory safety vulnerabilities have occurred in the last 50 years, and whose projects are 20 times more likely to have security vulnerabilities.

ooof.

[–] kurwa@lemmy.world 1 points 1 day ago (1 children)

You can do that in Rust with the unsafe keyword

[–] Maddier1993@programming.dev 12 points 1 day ago

but that's just a choice whereas in C you have no choice but write flawless code.

load more comments (11 replies)