this post was submitted on 13 Jun 2023
13 points (100.0% liked)

Rust

6024 readers
1 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
 

I'm a beginner who just started to read the rust book, I find it quite tedious and wonder how long does it take u guys to read it? Also, any suggestion after finishing reading the book?

top 16 comments
sorted by: hot top controversial new old
[–] [email protected] 6 points 1 year ago (1 children)

I guess that varies a lot with how much programming you've done before, particularly things like functional programming and using generics.

I can't remember exactly, but I think I took about a week with fully doing the little tutorial and the customising them.

I should probably go through it again; I'm sure there's a bunch of stuff I read and forgot, or never really grokked in the first place.

[–] howarddo 2 points 1 year ago (1 children)

Wow, that was quick. I heard that there's brown university version that have interactive quiz you should read as second run. Good luck

[–] [email protected] 2 points 1 year ago

It was a few years ago now, it could easily have been two or even three weeks!

[–] BaadC0de 6 points 1 year ago (1 children)

And after this book, I recommend "Rust for Rustaceans" by Jon Gjenset.

[–] howarddo 3 points 1 year ago

thanks, I'll add it to the list

[–] EdTheLegendary 6 points 1 year ago (1 children)

It took me several months at a rather slow pace, following along with rustlings. It's definitely worth being thorough though, it has been useful knowing what I do now when I'm working on my projects. A good follow up would be building your own project, preferably something you'll use yourself.

[–] howarddo 3 points 1 year ago (1 children)

thank, the fact that u can stick for several months is quite impressive though.

[–] EdTheLegendary 3 points 1 year ago

Thanks :) Good job making it as far as you have, keep going!

[–] kahnclusions 5 points 1 year ago

I never went through it "end to end". I think it's important to cover the essentials up to ownership, lifetimes, generics, etc, but most of the topics after chapter 10 you can pick and choose as you come across them in real life. The most important is to just start any kind of project and see what questions you come across as you build.

[–] jnovinger 4 points 1 year ago (1 children)
[–] howarddo 4 points 1 year ago* (last edited 1 year ago) (1 children)

yes, it's ubiquitous so I just call it the book :D

[–] ruffsl 7 points 1 year ago

It goes by: the Book. It must be capitalized. /s

[–] [email protected] 4 points 1 year ago (1 children)

I have never tried to read it from start to end. I went through first ~10 chapters then started to work on my projects. Then returned to some parts when needed more understanding. I noticed that some parts of the book were updated a lot during last 2 or 3 years, a lot of new information added.

[–] quavan 1 points 1 year ago

That is also the approach I took. I still haven't read every chapter despite using Rust professionally.

[–] ndotb 3 points 1 year ago

I plowed through it like a textbook on my first read, not really to absorb it 100% but to at least make the cadence and content familiar. I read it as a reference in parts on subsequent reads.

[–] lavafroth 1 points 1 year ago* (last edited 1 year ago)

I finished it on my third try (gosh, us millennials have terrible attention spans) in around two weeks. I think the takeaway comes from doing the exercises. I love the hands on approach of the book. You might wanna try out rustlings in parallel!