this post was submitted on 05 Jul 2025
317 points (98.5% liked)
Programmer Humor
25080 readers
856 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I will say this: for me, learning rust was 80% un-learning habits from other languages.
People tend to not like it when they have to change habits, especially if those took a long (and painful) time to acquire.
In this particular case, this is the same complaint Go faced with its form of explicit error handling. And Java, for that matter.
Honestly, Rust does a killer job of avoiding checked exceptions and verbose error hooks by way of the
?
operator, and requiring all possiblematch
branches to be accounted for. If you embrace errors fully, by usingResult<>
and custom Error types, your program gets a massive boost in robustness for not a lot of fuss. I recently learned that it gets even better if you embraceenum
as a way to define error values, and make sure it implements useful traits likeFrom
andDisplay
. With that, error handling code gets a lot more succinct, permitting one to more easily sift through different error values after a call (should you need to). All of that capability far exceeds any perception of clunkyness, IMO.