306

"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 122 points 1 day ago
  • 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.

[-] tatterdemalion@programming.dev 23 points 1 day ago

Your first point is not true. There are valid uses of memory sharing that rust will reject.

[-] smiletolerantly@awful.systems 6 points 1 day ago

Curious what you are talking about. Multi-threaded sharing of memory for example is also easy with rust, it just doesn't let you wrote and read at the same time, and so on.

[-] qaz@lemmy.world 1 points 1 hour ago

Classic example: A linked list

[-] smiletolerantly@awful.systems 1 points 46 minutes ago

... are entirely possible, even if rarely the right choice.

[-] sukhmel@programming.dev 7 points 1 day ago

Off the top of my head, single-threaded writing to the same memory from different fields of a struct. Not to mention self-referencing like if you want to hold a buffer and have different views into it in the same structure.

[-] jatone@lemmy.dbzer0.com 39 points 1 day ago

it always astounds me how utterly arrogant people are about their own abilities. (myself included) but seriously who the fuck doesnt like having something that just prevents you from doing things that are obviously broken and not going to work?

[-] i_stole_ur_taco@lemmy.ca 33 points 1 day ago

It’s like going to city hall and complaining your tax dollars are being spent on guardrails along the road that you haven’t personally ever driven into.

[-] Coldcell@sh.itjust.works 5 points 22 hours ago

Which, for the record, people fully actually do.

[-] numanair@lemmy.ml 1 points 14 hours ago

Saw someone genuinely saying this about potholes yesterday

[-] F04118F@feddit.nl 36 points 1 day ago

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 21 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

You can do that in Rust with the unsafe keyword

[-] Maddier1993@programming.dev 19 points 1 day ago

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

[-] Decq@lemmy.world 15 points 1 day ago* (last edited 1 day ago)

This so true, every one complaining that the borrow checker is annoying isn't apparently aware what they used to do was inherently flawed. Sure there a some, though rare, false positives. But they are easily mitigated. These people are exactly that what they themselves are complaining about, elitist.

[-] smiletolerantly@awful.systems 14 points 1 day ago

Yeah. Once you get used to the (verbose, but by no means unergonomic!) syntax, you'll probably never be happy with another language again. Job-wise, I am currently mostly using Go, and while also a nice language, I miss the confidence and security I took for granted with rust.

Not to mention just how goddamn expressive rust can be. Let bindings like if ok/err, else return? Assign from a match on Some(Ok(x))? Filter, map, and friends on any iterator? Oh my GOD the error handling with the question mark iterator? 100% confidence that if it compiles, no error, possible null value, or case is unhandled.

And all this WHILE giving you the amazing security benefits!

Ah, damn, caught me proselytizing again.

[-] mvirts@lemmy.world 3 points 1 day ago

Lol build something with serde and you'll be hooked for life

[-] smiletolerantly@awful.systems 4 points 1 day ago

Or a CLI with clap.

this post was submitted on 03 Aug 2025
306 points (95.3% liked)

Programmer Humor

25448 readers
1607 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS