3 ms·

Many things are worth investing in, if you justify it. The case between Rust and Go is an interesting one, as many of us have observed that the two languages s

Many things are worth investing in, if you justify it. The case between Rust and Go is an interesting one, as many of us have observed that the two languages seem to get paired together (for people wanting to learn). I wanted to start learning both beyond the basics, about 2 years ago. A few weeks ago I decided to write my Hello World in Rust, and I've been hooked. What I'd advise is for you to have a use-case that you work on while learning the language. You can spend a lot of time on the basics and std, but unless you start also picking up a few external libraries (e.g. SQL, web framework), you might find progress to be slow. The other benefit is that you'll get more exposed to the community. It's important to know where to go when you need to ask for help. In my case, I got comfortable with gRPC in Rust, then moved to Actix, and now (if I get diesel.rs to compile) I'm moving to SQL. Next will be "fearless concurrency", threading and futures, streams, integrating with NodeJS and other languages, etc. A roadmap which gets one comfortable with the standard language while being productive.

eslaught 8y ago
My advice would be to not just focus on a use case, but actually have a small "starter project" in mind that you can prototype an MVP for. My starter project[1] was a set of bindings for pandoc-types, so you can manipulate Pandoc ASTs in Rust. It's a very small library, but it's enough to plausibly do something interesting. It's also big enough to get me to play with serde and some serialization stuff in Rust. So it was a pretty good size to start with. https://github.com/elliottslaughter/rust-pandoc-types https://github.com/elliottslaughter/rust-pandoc-types [1]: Technically, I did work in Rust prior to this, but it was all long before 1.0, so I had to relearn when I picked it back up.

eslaught 8y ago

My advice would be to not just focus on a use case, but actually have a small "starter project" in mind that you can prototype an MVP for. My starter project[1] was a set of bindings for pandoc-types, so you can manipulate Pandoc ASTs in Rust. It's a very small library, but it's enough to plausibly do something interesting. It's also big enough to get me to play with serde and some serialization stuff in Rust. So it was a pretty good size to start with. https://github.com/elliottslaughter/rust-pandoc-types https://github.com/elliottslaughter/rust-pandoc-types [1]: Technically, I did work in Rust prior to this, but it was all long before 1.0, so I had to relearn when I picked it back up.