I want to learn Rust. There are so many resources available and I am unsure which one to go for, and if there are any tips on getting started?
I am a software developer by trade
Edit: Thanks for all the great replies!
As a wise person once told the Internet, don’t worry about picking the best one. But if you really had to pick one just start with the rust book. https://doc.rust-lang.org/book/ I would suggest to just dive in with a specific need you want to solve and instead of using your language of choice just use rust and look up stuff as you go. Hands on learning is usually the best learning. The only thing you need to “learn” is how to follow the ownership/borrowing paradigm that rust brings to the table.
I’m looking at this book now and I guess I’ll keep reading, but the early parts are quite verbose and I keep waiting to get to a description of the language. Something like “Rust for C++ programmers” might be worth a shot: https://github.com/nrc/r4cppp
There are a few different things like that for Ada. There are also a few “Rust for Haskell programmers” and I might look at a few of those.
There’s also Rust for the Polyglot Programmer which seems to be a generic version of those.
Thanks this looks good.
I second rustlings, it’s really good!
Was about to say this one, it is very good!
https://doc.rust-lang.org/book/ this is a great starting point. Then when you got the basics, and fiddled around a bit, then you can start looking for more specialized books (like Rust Atomics and Locks https://marabos.nl/atomics/ )
IMO the best way to start in a new language is to rewrite some of your previous projects in that language.
I generally start out by rewriting a couple simple 1-3 function console apps, basic leet code stuff like; palindrome, fizzbuzz, reverse an array in place, etc, and some simple unit tests for them. Then I go ahead and rewrite some of my previous projects or uni assignments in that language.
At that point I generally have a good understanding of basics and have an idea of how to approach a new project. When I got to this point in rust I then started on threading, async, why it’s easy to return a String and an ordeal to return &str, etc.
Please, don’t ever use async Rust lol :( it’s so terrible to work with closure recapture. There’s really one way of structuring your code to keep the borrow checker happy and I haven’t yet found it in my projects lol.
Yeah I would also recommend avoiding async Rust as much as possible. There’s really only a small number of situations where you need it - WASM, embedded (Embassy), and unfortunately most of the web ecosystem forces you to use it even if it isn’t necessary for 99% of people.
Sync Rust - even multithreaded - is absolutely fantastic at protecting you from mistakes & giving an “if it compiles it works” experience. Async Rust on the other hand is full of surprising and difficult to debug footguns.
- Combine iron with moist air.
- Wait.
Let’s not waste time! Add salt.
Save a little more and add some hydrogen peroxide!
Nitric acid!!
There’s also this!
!learningrustandlemmy@lemmy.ml
@sorrybookbroke@sh.itjust.works@maegul@lemmy.ml can probably explain moreCheers for the shout out! Yea the idea of that community is to be a kind of study group.
Whenever I’ve posted a thought or idea, that’s part question part experiment part pondering, I’ve gotten great replies from others.
Also two people have been running twitch streams of running through the book. Sorrybook is nearly done I think (they’ve been going for half a year now which is quite impressive).
The community is at a point now I suspect where some of us have learnt rust well enough to spread out into projects etc, so it’d be nice to work out how we can do that together at all.
Part of my initial idea with the community was to then have a study group for working through the lemmy codebase, treating it as a helpfully relevant learning opportunity … as we’re all using it, we all probably have features we’d like to add, and the devs and users of it are all right here for feedback.
Additionally, an idea I’ve been mulling over, one which I’d be interested in feedback on … is running further “learning rust” sessions where some of us, including those of us who’ve just “learned” it, actually try to help teach it to new comers.
Having a foundation of material such as “The Book” would make a lot of sense. Where “local teachers” could contribute I think is in posting their own thoughts and perspectives on what is important to take away, what additional ideas, structures or broader connections are worth remembering, and even coming up with little exercises that “learners” could go through and then get feedback on from the “teachers”.
Welp, YOU’RE frickin cool, kudos!
Cheers! Actually not sure exactly why you’re saying this (I’ll take the good vibes though) … but if you’re keen to join in in any way you are most welcome!
I was simply pleased by your comment, to see how much you care about helping folks and moving the community forward. Seems like quite a lot of effort to me, far more than I’d be able (willing?) to contribute, and I’m just forever grateful for folks you like you and wanted to say something about it :)
I appreciate the invite. I’m not at a point currently where I can put sincere effort toward much that’s non-essential, but if that changes, Rust is on my short list of targets for ways to spend some spare effort and time.
Cheers! Very much appreciate the love!
If you are looking to create a web service, I can suggest the zero2prod book. That’s how I learned rust and loved the process. I was also already a seasoned developer before taking interest into rust
A big part is kinda just doing it. I am trying to learn and it is kinda wild. I am currently working a warehouse job so it is hard to find the time. Try and go back and implement some of your favorite homework assignments in Rust.
I think a hard part of Rust is the mind shift. It just feels very different from anything else I have tired. I am doing some encapsulation for my learning, but it is not clear where to read about it and there are few examples out there.
I just found https://google.github.io/comprehensive-rust/ today. Structured course developed by Google for its Android devs.
I agree with the others who say to start with The Book – https://doc.rust-lang.org/book/
From there, start trying to create small things that you might want or need to do (parsing JSON is something that I needed to do and I started there).
From there, you will learn to fight the borrow checker and start to feel how rust is working. This will be annoying at first, but get better over time (at least in older versions of Rust; I haven’t used it in a while so it may be different now).
What is the borrow checker and why are people so frustrated by it?
Very TL;DR version: a variable has an owner. If you pass it off to another function, you no longer own it and can’t use it until/unless it gives the variable back. Rust can be really strict on making sure you aren’t trying to use something you don’t own at that time. The documentation explains it better than this (and I wrote a longer post but accidentally closed the window and lost it). See also mutability and lifetimes for some pain points people might not be used to.
Thanks for the answer!
Others have listed a bunch of good resources. If you are more of a visual learner, I have heard good things about the Easy Rust videos - https://www.youtube.com/watch?v=-lYeJeQ11OI&list=PLfllocyHVgsRwLkTAhG0E-2QxCf-ozBkk
The book is really good and offers a snapshot of those inner workings of the language.
For using it, LLMs (open weight and otherwise) perform very well and may fill the gap.
People already suggested it, but rustlings is awesome.
One thing I like to do is think of something I often do in another language, then Google how to do it in rust, i.e. dynamic dispatch. The way rust does it with traits is really interesting.
I started with the rust book and used chatgpt for any follow up questions I had.
