Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
The Rust Book provides a bottom up approach to learning the language. From your background, you'll probably be comfortable with a lot of things in it but it's definitely worth reading through to get insight on the unique features of Rust such as the borrow checker, lifetimes, traits, error handling, etc.
Learning Rust With Entirely Too Many Linked Lists which highlights a lot of the differences with how you need to structure your code in Rust compared to other languages.
Rustlings hasn't been mentioned yet. Rustlings contains small exercises which you should do along with The Book. The Book is the recommended way of learning Rust, but it's a bit theoretical, so Rustlings exercises help you to get your hands dirty and apply the things you learned.
Another good learning resource is the Tour of Rust, which is more hands-on than The Book. It has a code example (which you can edit and run directly) in every section.
“watched prime yell about VIM for hours” lmao well done, this got me. A lot of the resources people have already suggested are great! One thing I like to do after going through the documentation for a language is trying to build something like a simple rest api to get a better feel. Rocket (https://rocket.rs) and actix web (https://actix.rs) are popular web frameworks and then for ORM diesel (https://diesel.rs).
“watched prime yell about VIM for hours” lmao well done, this got me. A lot of the resources people have already suggested are great! One thing I like to do after going through the documentation for a language is trying to build something like a simple rest api to get a better feel. Rocket (https://rocket.rs) and actix web (https://actix.rs) are popular web frameworks and then for ORM diesel (https://diesel.rs).
“watched prime yell about VIM for hours” lmao well done, this got me. A lot of the resources people have already suggested are great! One thing I like to do after going through the documentation for a language is trying to build something like a simple rest api to get a better feel. Rocket (https://rocket.rs) and actix web (https://actix.rs) are popular web frameworks and then for ORM diesel (https://diesel.rs).
rust-learning (A broader listing that includes links to sites like Are we game yet? among other things)
The Little Book of Rust Books (An index covering most/all of the textual materials already linked, plus more like the Rust Performance Book, Rust API Guidelines, and The Rust Fuzz Book.)
rust-learning (A broader listing that includes links to sites like Are we game yet? among other things)
The Nomicon for learning the dark arts of unsafe rust 😳
C is much better specified than unsafe Rust. Some things are just not worked out yet in Rust. This may sometimes even bite very experienced devs, such as this issue with Box's aliasing semantics, which tripped up the author of left-right.
C is much better specified than unsafe Rust. Some things are just not worked out yet in Rust. This may sometimes even bite very experienced devs, such as this issue with Box's aliasing semantics, which tripped up the author of left-right.
Vim is great and all, modal editing feels more fluid to me, but it's an old program derived from even older ones, so the UX isn't the greatest. You need to invest time to get productive in it. One advantage is that there are vim-like keybindings everywhere, like on the Rust Playground, so I you decide to go that route, consider just using VS Code with the vim plugin. It will give you Code's affordances and let you skip the whole 'let's install a plugin manager to install lsp support so I can get it to work with rust-analyzer or wait maybe I should just use neovim how do I do a config that supports rust'. I use Helix myself – not only do I prefer its editing model, it's also easier to gete started with. For a ton of languages, LSP support just works if the lsp is on your PATH. If you press a key with further action required, a pop-up in the cornet lists available keys and what they do; if you press -?, a command palette appears.