Live data from Hacker News

How to Learn Modern Rust

github.com

1–10 of 67 posts

Re: How to Learn Modern Rust

#4
This is a good list, although it contains a lot of redundancy - at least, the first "how to learn" links - the youtube videos cover the same material over and over again. They are good - you may not need to watch every one in order as the author suggested.

My approach has been considerably, uhh.. lazier, if you will:

I just read through the rust book available on http://rust-lang.org. It is easy to follow although, sometimes it doesn't fully explain the "why" behind certain things to idiots like me. For that, I turned to a quick online search, which brought up helpful blog posts, Reddit and Stack Overflow posts.

Thats it. Next, I'll try to wrap my head around Actix to create a web server.

Re: How to Learn Modern Rust

#6

Is Rust old enough for there to be a 'modern' Rust?

Rust has improved in a number of significant ways since 1.0, those improvements are things that make it easier to work with in a number of ways. One way to think about this topic is if you found the language too hard in the beginning you may find it easier to work with now.

Also, since it was released a lot of patterns have evolved to work around the restrictions the language puts in place, and those are good to learn.

Re: How to Learn Modern Rust

#7

Is Rust old enough for there to be a 'modern' Rust?

Yeah, not really. The only big changes to the language core were non lexical lifetimes, match ergonomics, lifetime elision, auto-deref, and async, although all of these are already so old now that I wouldn't consider them constituents of modern Rust; they're just (unqualified) Rust at this point.

Releases tend to bring some minor improvements like functions you wished had always existed or making non-const functions const, but that's pretty much it. Rust is a remarkably stable language.

Re: How to Learn Modern Rust

#9
My first piece of advice is to just start writing code.

If you are not specifically interested in super high performance systems level code, my second piece of advice would be to write code that avoids lifetime annotations until you get the basics of the borrow checker down.

For me, this meant writing a gRPC API with Rust using `tonic` with a `diesel` based persistence backend and observability with `tracing` and `opentelemetry`. This gives you a good survey of the basics and you'll learn about all of the core traits and language features in the process.

Post reply on HN