Steve Klabnik is the Community Team Leader for the Rust team at Mozilla, in charge of official Rust community documentation as well as the key Rust community advocate. Klabnik is a frequent speaker at conferences and one of the world's most prolific contributors to Rails projects.
Carol Nichols is a member of the Rust Community Team. She's been active in the Rust community and is an organizer of the Rust Belt Rust Conference.
This is ‘the’ book for Rust. Buy others as well, but this is a perfect starting point. It may be freely available in electronic form elsewhere (including the actual Rust website), but I’ve always found paper books to be a better learning tool than anything read from a screen.
5つ星のうち5.0One of the best programming books ever ...
Rust is important and becomes more important every day, unfortunately, there are not many books out there, but this one is kind of outstanding. Instead of summarizing the old programmers' paradigms it directly starts to highlight the advantages of Rust and carefully introduce the cargo environment. I really love it.
However, it is not desigended for complex applications like numerical/ AI or parallel backend development. Here we have to wait for another issue ...
I hate reading from a monitor so I bought this copy. This is basically the printed version of the open source book. More convenient to read in my opinion, especially during trips to the throne. Rust is the C/C++ killer and this is a great introductory book.
Das Buch ist wirklich sehr gut geschrieben und angenehm zu lesen. Es gibt einen guten Einstieg in diese Programmiersprache und der Preis ist wirklich sehr gut für diese hohe Dichte an Informationen, jedoch würde ich es keinem Programmieranfänger empfehlen. Ich kann es wirklich nur sehr empfehlen.
5つ星のうち5.0A great step into a New language, but not a First language.
[8/25/19] A few chapters in and the book is well-written and easy to follow. It gives great explanations and doesn't often leave you wondering. Where it does, however, it makes a point of mentioning that more will follow. The only criticism, currently, is that the book does not seem written for new coders. While explanations are given line by line, basic concepts are not explained in ways you would expect of a beginners book.
[10/5/19] Still going through the book, but it continues to follow with my original comments, mostly. I did however find Chapter 7 to be a little lacking in thorough explanations. Nothing major, but it did leave to some light confusion. In addition, this language is certainly a learning curve in terms of coding-style from most (if not all) other languages out there.
[12/24/19] So, I am no expert, but I'm onto the next book. This was a great read and a great new language. Coming from C++, this is the first language I have been excited about in a long time!
5つ星のうち3.0Thorough introduction for practicing programmers, with a few warts.
This is a very good book that should have been superlative. It's geared toward existing programmers, and aims to highlight the particular features of Rust that would entice one to take up the language. It is a thorough introduction, and once the reader finishes, they should know enough about the language and its idioms to continue learning on their own and write robust, efficient programs.
NONETHELESS, there are two things I don't like about the book, and they both relate to the example code. Far too many times, a concept is introduced or illustrated with a section that reads:
"Here's how you use construct *x*: [sample code using construct *x*] -- As you can see, the code didn't compile. That's because whenever you *x*, you also have to *y*."
I don't care for that style one bit, especially since I'm likely to make my own errors anyhow. I'd rather have sample code that works, and then, if necessary, add a line such as "note that if line such-and-such said this and not that, the code wouldn't compile."
The second issue is also related to sample code, where the example introduces multiple new concepts with no forward referernces. Something like:
"We will now show you construct *x*: [sample code using construct *x*, *y*, and *z*] -- Note how we also use constructs *y* and *z* in this code."
I'm the sort of reader who, if he sees something unfamiliar in sample code, assumes he's missed something in the previous pages, and starts casting back and forth to see what it was. Even if the very next sentence mentions the other constructs, I'm working in a different mode when I'm studying code samples and don't see it. It turns out, I didn't miss anything, they just threw multiple things out at once without notifying the reader. A simple "We will now show you construct *x*; note that constructs *y* and *z* also appear in this example" would have saved some time and worry.
Forewarned, however, the reader will find a lot of useful information about Rust, and from people intimately familiar with the language and its development. I recomend it, I just wish the sample code were a little more user-friendly.