A guide to aid you in your journey of becoming a Rustacean (Rust developer). See the Contributing and Code of Conduct for more information about how to contribute to this repository.
Rust is a modern systems programming language with safety in mind as one of its core goals and strengths. Systems programming is programming within a resource contrained environment. However, as a lot of our services run now in paid-for-usage cloud environments, we can also consider them as resource constrained environments. This is why Rust is a great fit for more use cases then people might realize.
As it is a modern language and has taken the lessons from many other languages before it, it is also surprisingly pleasant to use once you get the hang of it. It's type system also allows expressive code that can help you exclude a great categories of bugs beyond the benefits that static typing can bring.
The goal of this guide is to introduce Rust to you as an individual or an entire organization. Should this not be sufficient you can also contact me for 1-on-1 coaching or workshops for your organization, by emailing me at glen@plabayo.tech.
Rust 101 Course
The origins of this guide can be found in the preparation of a semester long course I gave to a group of employees at OTA Insight Ltd.. The recordings of this course are available on YouTube at: https://www.youtube.com/playlist?list=PLQgXEsLXFxpVyLddG8FFXfNQEiodTzAjj.
This course is still actively being thought and the videos will be uploaded weekly when I find time to upload the recordings.
Learning Rust in Milestones
┌───────────────────────────┐
│ │
┌───────┴──────────┐ │
┌───────────┬─────────────►│2. Learn More Rust├─────┐ │
│ │ └────────┬─────────┘ │ │
│ ┌─────┴───────┐ │ ▲ │ │
│ │1. Learn Rust│ │ │ │ │
│ └──┬──┬───────┘ ▼ │ │ │
│ │ │ ┌────────────┴──────┐ │ │
│ │ └─────────────►│3. Learn Async Rust│ │ │
│ │ └─────────┬─────────┘ │ │
│ │ │ │ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌────────────────────────────────────────────────────┐ │
│ │4. Study Using the "Zero to Production in Rust" book│◄──┤
│ └──────────────────────────────┬─────────────────────┘ │
│ ▲ │ │
│ │ │ │
│ │ ▼ │
│ ┌─────────────────────────────┴─────────────────────────┐ │
│ │5. Contribute for the first time to an existing project│◄──┘
│ └──┬─────────────────────────────┬──────────────────────┘
│ │ │
│ │ ▼
│ │ ┌───────────────────────────────────────────────┐
│ │ │ 6. Study using the "Rust for Rustaceans" Book │
│ │ └────────────────────────┬──────────────────────┘
│ │ ▲ │
│ ▼ │ ▼
│ ┌──────────────────────────────┴────────────────────────────┐
└─┤7. Contribute an advanced feature or start your own project│
└──────────────────────────────────┬────────────────────────┘
│
▼
┌──────────────────────┐
│ 8. Continue to Learn │
└──────────────────────┘
Continiously Learn, Take Your Time
Enjoy the road :)
Sponsors
Support this project by becoming a sponsor.
Index
About
Glen De Cauwsemaecker created this Educational track to help you get started with Rust from an absolute beginner all the way until you’re an expert in it. He is open to mentor people, lead workshops and more. If you’re a team lead that wants to introduce Rust to their team, feel free to talk to him. Glen started with Rust around 2015, when Rust was still unstable and fast moving. Coming from a C++ background in a system programming job the benefits were immediately clear to him. In the meanwhile things have changed a lot and many companies have been starting to adopt Rust in their toolset:
- Amazon Web Services (AWS) has used Rust since 2017 for its serverless computing offerings, AWS Lambda and AWS Fargate. With that, Rust has gained further inroads. The company has written the Bottlerocket OS and the AWS Nitro System to deliver its Elastic Compute Cloud (EC2) service.
- Cloudflare develops many of its services, including its public DNS, serverless computing, and packet inspection offerings with Rust.
- Dropbox rebuilt its backend warehouse, which manages exabytes of storage, with Rust.
- Google develops parts of Android, such as its Bluetooth module, with Rust. Rust is also used for the crosvm component of Chrome OS and plays an important role in Google’s new operating system, Fuchsia.
- Facebook uses Rust to power Facebook’s web, mobile, and API services, as well as parts of HHVM, the HipHop virtual machine used by the Hack programming language.
- Microsoft writes components of its Azure platform including a security daemon for its Internet of Things (IoT) service in Rust.
- Mozilla uses Rust to enhance the Firefox web browser, which contains 15 million lines of code. Mozilla’s first two Rust-in-Firefox projects, its MP4 metadata parser and text encoder/decoder, led to overall performance and stability improvements.
- GitHub’s npm, Inc., uses Rust to deliver “upwards of 1.3 billion package downloads per day.”
- Oracle developed a container runtime with Rust to overcome problems with the Go reference implementation.
- Samsung, via its subsidiary SmartThings, uses Rust in its Hub, which is the firmware backend for its Internet of Things (IoT) service.
The language and its ecosystem have also very matured. Concepts like Async have also landed and Async runtimes such as Tokio have become stable and can be used without fear. While it was harder to convince companies to jump on the Rust wagon in the past, by now it should be a lot easier to sell. Is it one language to replace them all? Of course not, but neither should it be overlooked. Are you not sure how Rust might benefit your team for one thing or another? Contact Glen and figure it out together.
If you are a bit of a history nerd you might also enjoy:
There’s a last section on the end of the Rust learning content. This one contains useful references and sources that you can check as part of your continuous journey as a capable Rust developer.
Python / Javascript Developers
In case you come from Python or Javascript you can alternatively replace the first four steps with a single book. Rust Web Programming (Packt Publishing) aims to get web developers (including Python developers) get started with Rust and has a very pragmatic approach.
Given how important Async is in our work environment it is still worth to go through section (3) “Learn Async Rust” to make sure you do really grasp that very well. It is also where a lot of your Rust knowledge starts to come together, so if you get that you know you’re on the right track.
Should you after completing this book (even if partly) want to have some more hands on experience you can opt to never the less do section (4) as well and go through the “Zero to Production in Rust” book
However, in case you are confident you did get all the foundational concepts of Rust and want to just develop stuff already and get it “into your fingers” you might want to opt to after this (and before jumping onto section (5)) read “Rust In Action” first. It gives a lot of fun things to build. Alternatively you can check the “Learn More Rust: Extra” part of section (2) Learn more Rust, where we also go over many ideas for you to get more experience and help you solidify your Rust knowledge.
The “Rust in Action” book can also be seen as yet another alternative all together, as it is also aimed at introducing Rust to people who never did any Systems programming, So you could also do it instead of the Rust Web Programming book.
1. Learn Rust
In case you're new to the language we suggest you to take a look at Learn Rust (free):
ⓘ Hardcore alternative
Programming Rust, 2nd Edition (O’Reilly Publishing) is a big book and will take you some time to get through. It is not for the faint of heart. However… If you do choose for this route as an alternative to (1) Learn Rust, you will absolutely not regret it. In fact, your entire rest of the Journey will be a breeze.
The “Programming Rust, 2nd Edition” book is a gem and in case you can handle big dry Technical books such as these it is one that will give you just as much love back as the energy that you put into it. Take your time, get through it, play with it, and enjoy. In fact, it can be easily paired with Rustlings by doing the exercises linked to the content you’re reading. Rust by Example can also be added on top of that to see some more code related to the stuff your learning.
Soak it in. It’s a hardcore alternative, but if you’re up for it, it’s there for you to grab.
If you’ve never done any Systems programming before, this will be an especially helpful book given it will explain a lot of the magic you’ve encountered in your very protected professional life so far. You’re welcome.
Questions you should be able to answer at the end of this step:
- Rust is a Memory-Safe language. How? Why? In what way is this different from other Memory Safe languages such as Go?
- Rust is a performant language. Why can it claim this. How?
- How do you structure data in Rust?
- Is data passed by Reference or value in Rust? And what does it mean?
- Is data mutable or immutable by default? How do we make it the other way?
- What are traits and how are these related to the data models that you structure in Rust?
- How can you extend the behaviour of external types?
- Can you extend behaviour of external types using external traits? Why or why not?
- What is a constant? Where can we define these?
- What is a static variable? How is it different from a constant? What’s special about mutable variables?
- How does Rust support Async Rust? How do you use it? What are Futures?
- How do you achieve parallel programming in Rust?
- What’s the difference between async programming and parallel programming? How are they related?
- What is the borrow checker? What is ownership? How are these concepts related?
- Data can be moved and it can also be dropped. What do we mean with this? How do we have control over this?
- How do we achieve shared mutable references to the same data? How can this be done safe?
- What are lifetimes? How do they work? Can you give some examples of where these are used?
- What are generics? Why do we use them?
- What are Rust Macros? When do we use these? What type of Macros are there?
- How do you build Rust projects?
- How do we use dependencies of other developers into our projects? And how do we call such dependencies?
- What are sum types? What are product types?
- What is an Enum in Rust and how can we use it? How can we define it?
- What is pattern matching in Rust? How do we do it? How is it more powerful than a switch?
- How do we write tests in Rust? What kind of tests are there?
- What are closures and how are they related to functions? What they have in common? How do they differ?
- What kind of smart pointers does the Rust std library provide you? What are there use cases, differences, and so on?
- What is unsafe Rust? How do we use it? When do we use it? What guarantees we still get, even when using unsafe Rust?
Alternative or Companion resources
Welcome to Comprehensive Rust 🦀 - Comprehensive Rust 🦀: a small bootcamp course by Google focussed on Android Engineers. Most of it is however applicable to anyone coming to Rust from another language and could be a great alternative or companion for some of the resources above.
2. Learn more Rust
Questions you should be able to answer at the end of this step:
- Make sure to be able to answer all questions of step (1).
- What is cargo and why does it exist?
- What kind of extensions exist for Cargo, how do we install them, how do we use them and what are some commonly used ones?
- What is the Cargo.toml file?
- What is the Cargo.lock file?
- What are build scripts? Why do we use these? How do we use these?
- How can we build code? How do we test code?
- How can we check code without building the final binaries?
- How do we make a simple CLI application? How do we pass arguments and flags? How do we handle signals?
- How can we structure our code and package(s)?
- What does public and private mean in the context of Rust? At what scope do these operate?
Learn More Rust: Extra
Once you went through the resources in the previous two chapters you might want to start working on a real project to start applying and solidifying your knowledge. A classic way to do this is by porting a small specialized codebase from one language to Rust, keeping in mind to not 1-to-1 map the lines of code but to instead focus on porting the logic with the “Rust way to do things” in mind.
Should you want some inspiration or a more guided approach, here are some resources that could help you out with this extra optional, but recommended step:
- Command-Line Rust: build a cli tool such as grep in rust, using test driven development (TDD), all to learn Rust
- Rust Application Books - The Little Book of Rust Books: lists a lot of different books, including ones that allow you to develop small projects using Rust, usually in a well guided fashion;
- Introduction - PNGme: An Intermediate Rust Project is an especially fun small project. It allows you to apply the knowledge that you learned above in a very narrow program, that is for once not network related. At the end you’ll have a cli tool that allows you to encode and decode “hidden” messages in a PNG image;
- Introduction - MacroKata: Macro’s are in general not very covered in the resources above, as it is not that common that you have to write your own macros. They can however be convenient in certain situations. This book can be seen as a bootstrap tutorial to get you started with one kind of Rust macros.
- If you are interested in (also) learning procedural macros you can perhaps consult the following resources:
- And of course do not forget to consult the “classic” macro Rust book: The Little Book of Rust Macros
- If you want to get a quick intro and overview of Macros this video can help a lot as well: Rust's Witchcraft
If you have a lot of free time at your hand and you want to build something really cool that is totally useless, here are some more ideas:
Seriously though, do not consider the above recommended or mandatory in any way. If you however really like to develop stuff and you do like to do it extensively in your free time, then, and only then, I do believe that the above are a great way to really solidify your current Rust knowledge and give yourself a great (pragmatic) foundation.
Code like a pro in Rust
At this point of your Rust learning journey you’ve come a far way already, relatively speaking. Perhaps you want to shortcut, at least for now.
If so, the still to be published “Code like a pro in Rust” book might be enough for you to quickly get from beginner to advanced Rust programmer.
A Crust of Rust
Once you get at this point you are around the level of a beginner or intermediate Rust programmer. At this point you could already start to tackle stuff like “Rust for Rustaceans” of step (6). However it might be a bit much.
Therefore while you go through the next couple of sections it could be helpful to now and then (e.g. while washing dishes or instead of Netflix) an education Rust code video. In the appendix at the bottom of this page there a couple of such suggestions.
Particular to this context you might want to save the “Crust of Rust” playlist. Each video will go over a specific topic, e.g. Lifetimes, macros, Atomics, … No need to watch them one by one, feel free to jump to them in whatever orders and only those that interest you (which is the same tip that I can give for the "Rust for Rustaceans" book).
3. Learn Async Rust
There is no standard / official Asynchronous runtime. This in contrast to actual CPU threads which you can create from within the std library.
The most popular and recommended by many Async Runtime is the Tokio runtime. Which brings us to the next chapter:
Please also join the Tokio Discord community as part of your async Journey, a place where you can ask any questions you want as well: https://discord.com/invite/tokio. It will be a place you want to be in once you start working for the Crawler team on RSProxy and its dependencies.
As an extra you may also want to read and develop alongside the following articles:
ⓘ Note: Tokio also provides support to the new Linux kernel io_uring concept, a new powerful way to allow async programming on Linux. Support for it can be found at: GitHub - tokio-rs/tokio-uring: An io_uring backed runtime for Rust
Synacktiv made an IO network scanner using io_uring as can be seen at GitHub - synacktiv/io_uring_scanner: io_uring based network scanner written in Rust, using tokio’s low level userspace bindings to io_uring.
Questions you should be able to answer at the end of this step:
- How does Async programming work in Rust, if you didn’t understand this already?
- What types of concurrent programming does Rust support? How many are there in general?
- What are Futures and how do they work? What function they have? How do they affect you?
- What is Send and Sync? What is it used for? How does it affect you?
- What are good use cases of Async code? What kind of tasks aren’t a good fit for this?
- What are Async Executors? What are Async Runtimes?
- What is Tokio? How do you use it? What does it give you?
- What are some other libraries in the Tokio ecosystem?
- What can you build with Tokio?
- Why would you use Tokio?
- How do you achieve Rust programming with only standard code (meaning code developed by the Rust core team)?
- Why does Rust not bundle an Async runtime?
- What is parallel programming? How do you do it in Rust? How does it relate to Async programming?
Tower
Once you step into the world of Async Rust, Tokio and Web Services you'll sooner or later come across Tower, in a similar fashion as Serde blew your mind away for your serialization needs. Yes it did, you can admit it, this is a safe space.
Tower is a library of modular and reusable components for building robust networking clients and servers.
With Tower everything is a service. A service takes in a request and outputs either an error or a response. What the actual types for these request-response pairs are, is up to you and depend mostly on the layer it is used.
In tower it is typical that a service wraps another service, called "layers", as such all your services and middleware will stack on top of each other, like a... tower.
Rust Atomics and Locks
Understanding concurrency, the primitives used to do so safely and how it all works “under the hood” (e.g. the OS level) is not critical but it will help you big time the rest of your Async professional career.
The book “Rust Atomics and Locks” by O’Reilly is an amazingly good book by Mara Bos, an important Rust Contributor. Going through the book will take you some time despite its smaller size, but doing so is very rewarding. As with any technical book it is best to read this book as well as do its exercises and apply its knowledge using one program or another. Learn, Apply, Repeat. Play with it, Understand it.
This book is so good, that even Go, Python or JS developers that will never ever touch Rust, might want to learn Rust just to understand the knowledge that can be found in this Gem of a book. Read it. You won’t regret it.
As it is more advanced knowledge it can however be seen as “Extra”, so in case you are in a hurry to finish section (3) of the Rust track, feel free to skip it. But even if so, keep its existence in mind and come perhaps back to it when you start to get yourself into trouble.
Questions you should be able to answer at the end of this extra step:
- What primitives are there in general to achieve concurrency?
- What primitives does the OS give you?
- What is the difference between threads and async programming?
- Why is async programming faster?
- When would you use threads? When would you use async programming?
- What’s a Mutex? How could you implement one?
- What’s a Conditional Variable? How could you implement one?
- What’s a Signal? How could you implement one?
- What’s a Channel? How do you implement it? What types of channels are there?
- What is Reordering? How can we deal with this? How does it affect us?
- How can we efficiently make a thread go to “Sleep” and have it woken up again?
- What’s a Spin Lock? How do we build one?
- What’s an atomic? What kind of atomics are there? How do they work under the hood?
- How does Rust achieve thread safety?
- What’s Memory Ordering? What’s the Memory Model? What types are there? Which ones can you use?
- What is Aquire and Release? What is this an example of?
- When we talk about a “happens-before relationship”. What do we mean with it? Why is it important?
- What is caching in context of your CPU? How does it affect us? What can we do about it?
A Note About the remaining part of this guide
The next sections are all optional and are not required to really be productive in Rust. Some of it are alternative resources or extra content to learn from. Others is just miscellaneous content that is not really required to be productive in Rust, but might be interesting to you.
This guide is either way not meant to be read in a single session or series. Take it as yours and just use it as part of your learning journey. Take your time as learning Rust isn't easy, but it is a very rewarding one once you did climb the mountain and are dancing with a double rainbow in the background.
4. Study using the “Zero to Production in Rust” book
Go through the entire book, filling any gaps you might still have and do all the exercises as well.
At the end of the book you should be able to present your own GitHub or GitLab hosted projected based on the exercises and projects of the books, where you applied all your knowledge and also put in something of yourself in it.
ⓘ Backend frameworks like Rocket and Actix are pretty commonly used in books. However know that the Axum framework is currently probably your best best if you need to choose a backend framework for your next or current Rust project.
Questions you should be able to answer at the end of this step:
- How can we write a Full stack app in Rust?
- How can we deploy and host a Full stack Rust app in the cloud?
- How can we add telemetry?
- How can we interact with Databases using Rust?
- How can we debug production-quality Rust applications?
- How can we test Rust applications?
- How do we make Async applications in Rust?
- How do we achieve TLS capabilities with Rust?
- How do we make a web server with Rust?
- The book uses Actix. What are some alternatives these days?
5. Contribute for the first time to an existing project
Contribute to an open source project that you like or may want to strongly depend upon in the future.
Many projects have a good first issue label, which is a good place to start. You can also look for issues that are labeled help wanted or easy.
There's also the Rust Mentorship program, which pairs up new contributors with experienced Rustaceans. You can find more information about it at: https://rustbeginners.github.io/awesome-rust-mentors/
In The weekly Rust Newsletter you can find a list of projects that are looking for contributors.
If you are a seasoned programmer already you might also opt to already start making your own new project or parting a scoped project from another language to Rust.
6. Study using the “Rust for Rustaceans: Idiomatic Programming for Experienced Developers” book
Go through the entire book, getting a deep(er) understanding of the advanced concepts and inner workings of them.
At the end of the book you should be able to present your own GitHub or GitLab hosted projected based on the exercises and projects of the books, where you applied all your knowledge and also put in something of yourself in it.
Questions you should be able to answer at the end of this step:
- Be able to answer all questions from previous sections, in full confidence and in a lot more depth than you could do before.
- How is memory laid out for your Rust Data structures? Can you control it? If so, how?
- Explain in full detail so someone new to Rust can understand it what borrowing and lifetimes are, how do they work, why are they important, how do they affect us, how do we encounter it, why do we use it?
- What primitive types are there in Rust and how are they laid out in memory?
- What is the Orphan rule? Why is it important?
- What is polling in the context of Asynchronous programming?
- List some additional testing tools beyond unit tests? Why does each one of them mather?
- What is Pin and Unpin?
- Note: Rust of Crust also has a great video about it should you need some more explanations about this tricky concept;
- Why is Asynchronous programming more complicated than parallel programming?
- How can you test your Asynchronous code? And because it is Rust, what kind of Asynchronous problems do we not need to test if we structure our code right? And why not?
- In the context of concurrent programming, what are actors?
- Bonus question: why do some people see this as the future?
- what is FFI? Why do we use it?
- What is Rust without the STD? How do we use it and why?
- What are some common patterns found in the wild and that are discussed in the book?
- How can you continue to learn Rust?
7. Contribute an advanced feature to an existing project or start a project from scratch
Start a project for yourself, your dog, your organization or mother. This might be a microservice, library or small tool. Everything is possible.
Another option is to contribute to an open source project that you like or may want to strongly depend upon in the future.
See section (5) about your first contribution for some inspiration on where to start.
Appendix
Appendix I. Install Rust
In order to start using Rust you have to install and configure its tooling on your machinery.
- The Rust compiler (
rustc), standard library and tooling (e.g.cargo) are all managed usingrustup.- You can learn how to get started by going to: Getting started
- Once you finished with this you’ll have Rust ready on your machine out of the box. Each time there is a new version of Rust you can update it, simply by running
rustup update
With this installed you should now be able to run the following command:
Which will output something like:
cargo 1.67.1 (8ecd4f20a 2023-01-10)
You can learn to create, compile and run your first Rust program at "First Steps with Cargo - The Cargo Book".
Linting and styling
- Install
clippyusingrustup component add clippy- This way you can use the command
cargo clippyto help guarantee the quality of your code
- This way you can use the command
- Install
rustfmtusingrustup component add rustfmt- This way you can use
cargo fmtto format your code (best to also configure this in your IDE to be done each time you save the file)
- This way you can use
No custom linting configurations are agreements are required. If you use these two tools, you’re golden. These tools also work nicely with any IDE you might use. Within your CI environment these same tools will be used to check that your code adheres to its standards.
Appendix II. WebAssembly (WASM)
WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications.
WebAssembly on itself is completely isolated from Rust, but it must be said that among the WASM community, the Rust part is probably the biggest and most active one. Compiling Rust to WASM is a true pleasure and allows for browser client code to be written in Rust, be it a small library to be used from JS or an entire web client. WASM projects can also be used to quickly deploy web services (in the backend). These are similar to lambda functions but are even faster to use and in a way also safer.
WASM Learning Resources
Frameworks that you might want to check if you want to make a front-end (web) app using Rust:
Run WASM Backend Services in the cloud:
Appendix III. Native Apps
Native apps are applications written for a specific platform. While that could be any platform, it usually refers to anything that is not the “web” and even more so, these days, it pretty much always refers to Desktop, Mobile or the combination of. Cross platform apps mean that multiple platforms are supported, which could be any set of web or non-web platforms.
Tauri
Tauri is the toolset you want to check out if you want to build native apps with a Gui in Rust. You can find all information about it on their official website: https://tauri.app/
Build an optimized, secure, and frontend-independent application for multi-platform deployment.
Tauri applications can be compared to Electron, but it uses a very different approach. Multiple rendering engines are supported, with web view like rendering engines being the default. But this is still different then shipping a Node runtime and Chromium with each and one of your apps. Meaning your desktop applications can be as small as a couple of megabytes, compared to the usually bloated 150MB apps. And once running they will also be a lot less resource hungry compared to your topical Electron app.
Mobile applications are not yet officially supported, but they will soon get support as well, as the underlying technology for it is already more or less ready.
In case you want to write applications that work on both the web and a non-web platform you can achieve this by splitting of your business logic from your minimal front-end logic, such that you can write one front-end in any of the available front-end approaches (e.g. leptos or perseus) and another one using Tauri, with most of your code being available as one or more Rust libraries.
The front-end logic can be written using any web application front-end framework, e.g. Svelte.
You can also opt to go fully native by using plugins such as tauri-egui: https://github.com/tauri-apps/tauri-egui
Appendix IV. Rust in the background
As with any (new) language, there’s no point in replacing every existing technology written before, with a new implementation written in Rust. While at times there are benefits such as with ripgrep instead of grep, this is not a generally useful strategy not a desired one.
- In Appendix I. we already saw that Rust can be compiled to WASM, and as such you can build an entire WebApp in Rust. However instead of replacing your entire WebApp, it is also just as well possible that you only replace the components of your App where it makes sense, e.g. where you need to do a lot of computations;
- In Appendix II. we learned about Tauri to build native apps with Rust, and also here noted that it can be done while at the same time building your core frontend logic in the frameworks you are used to;
At times however you might be able to incorporate the benefits of Rust in your existing benefits without having to expose the language to anyone:
- FNM is a replacement for NVM. While the latter is more powerful the first is a lot faster, which speeds up terminal start up times by a lot, just to give one benefit;
- Deno can be used as a replacement for NodeJS, and can not only run javascript but also typescript (for which you would otherwise use something like ts-node). It is not a 1-to-1 replacement, and it will require some effort, but it is already today a faster and more secure alternative;
- SWC is a speedy light alternative to babel, with the first outperforming the last with its eyes closed and 1 foot still in the bed;
These give just a small taste of what Rust can mean for Web developers even if they do not know or use Rust themselves directly.
A language is a tool, but a tool is not to be applied to any problem. Rust has its advantages and use cases, it would be foolish not to use it where desirable.
Appendix V. Next Steps
Learning to master a language has a beginning but it doesn’t have an ending. You’ll want to continue to learn, teach others and keep up to date.
Keep up to date
Official Blogs:
Conferences:
Podcasts:
- Rustacean Station is a pretty great podcast with very interesting guests and even more interesting knowledge to share. Listen to it, you won’t regret: https://rustacean-station.org/
- In order to learn Rust you can also listen to the New Rustacean podcast, which is a podcast about learning Rust: https://newrustacean.com/
- It no longer airs, but its content remains useful and available
Actuality:
- “This week in Rust” is a weekly newsletter helping you stay up to date with Rust from the lazy comfort of your Mailbox. Easy peasy. They can also be read online in case you prefer a browser instead of the web or do not want to subscribe for w/e reason.
- Blog articles from the community get shared here as well, some accessible to new comers to Rust, others a bit more advanced
- They also share VOD’s of recent conferences, e.g. the issue in which they share the rust talks from FOSDEM 2023: This Week in Rust 481 · This Week in Rust
- “Rust Magazine”: an online magazine dedicated to Rust
Lists
community curated crate lists:
Read
Free Rust Resources that we haven’t mentioned yet, but are great to read at one point or another:
If you learn by doing and haven’t gotten enough from the resources we linked already in “Learn more Rust”, here are some more tips:
A blog you might want to RSS subscribe to is Amos’s his blog which is always fun to read, be it sometimes a bit heavy: https://fasterthanli.me/tags/rust/
A nice reference sheet if you need one can be found at: https://cheats.rs/
Educational
- Crust of Rust video series by “Jon Gjengset”, for those that want to see an experienced Rust Developer work through problems: Crust of Rust
- If you like to learn by watching you can find a Rust streaming list at https://github.com/jamesmunns/awesome-rust-streaming/
- Interesting youtube channel with a lot of great stuff to learn about Rust: https://www.youtube.com/@NoBoilerplate
- If any of the basic (textual) learning resources from the actual learning journey didn’t quite work for you, you might find a video course more useful. If so, here are two of them:
- If you need inspiration on things you can build with Rust to get the language in your fingers as well as learn how software that you use is implemented, you might want to check out: https://app.codecrafters.io/tracks/rust
- Learn Full Stack Rust Interactively: Rust Insight! - an interactive book for practicing Rust on the laptop (early access)
- A big index of many more learning resources, named aptly “How to learn Modern Rust — A Guide to the adventurer”: https://github.com/joaocarvalhoopen/How_to_learn_modern_Rust
- Do not take the list as-is and use mostly as inspiration. No need to really do all on that list, but if you need more learning resources, there is plenty of good content and inspiration in there!
- Black Hat Rust book: https://kerkour.com/black-hat-rust (could be nice for inspiration on some hands-on experience while becoming more familiar with Rust)
- If you want to test your Rust concept skills you might also enjoy taking the Rust Quiz. The more answers you have wrong the better, as it means you’ll learn new things from the explanation :)
- If you want to learn by doing by contributing to an existing Rust OSS project (including the Rust language and tooling) you can try to find a mentor to help you for free online in achieving this, by going to Awesome Rust Mentors: https://rustbeginners.github.io/awesome-rust-mentors/
from Hacker News https://ift.tt/nFPuVHB
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.