←back to thread

Flattening Rust’s learning curve

(corrode.dev)
451 points birdculture | 1 comments | 13 May 25 22:25 UTC | HN request time: 0.204s | source
Show context
mdwhatcott ◴[14 May 25 01:17 UTC] No.43979711[source]▶
[flagged]
replies(13): >>43979747 #>>43980029 #>>43980452 #>>43980582 #>>43980897 #>>43981065 #>>43981118 #>>43981329 #>>43981636 #>>43981787 #>>43981862 #>>43982909 #>>43992716 #
bsder ◴[14 May 25 06:05 UTC] No.43981329[source]▶
> If a language needs an article like this, absolutely begging people to bite the bullet to learn it, maybe that's a language design smell.

The problem with articles like this is that they don't really get to the heart of the problem:

There are programs that Rust will simply not let you write.

Rust has good reasons for this. However, this is fundamentally different from practically every programming language that people have likely used before where you can write the most egregious glop and get it to compile and sometimes even kinda-sorta run. You, as a programmer, have to make peace with not being able to write certain types of programs, or Rust is not your huckleberry.

replies(2): >>43982704 #>>43983778 #
1. empath75 ◴[14 May 25 12:37 UTC] No.43983778[source]▶
> There are programs that Rust will simply not let you write.

If you're writing purely safe code, I will say this is true in a practical sense, but you can almost always use unsafe to write whatever you think rust won't let you do.