News for hackers. Stuff that matters.
Re:Rust's 2017 Roadmap by adamnemecek on Monday February 06, 2017 @03:59PM (#13583851)
> Plans include a new book,

You should consider publishing an official, printed book. I would totally pay $30-40 for something like this. And once it's already written, the actual publishing shouldn't be too time consuming (but idk lol). I think that there's a lot of people who'd buy it just to support the project.

On one hand, I do have environmental concerns, but on the other hand, I feel like my retention rate with print is like 70% as opposed to like 40% with digital.

Re:Rust's 2017 Roadmap by aturon on Monday February 06, 2017 @04:04PM (#13583907)
The new book will be published by NoStarch press!
Re:Rust's 2017 Roadmap by Animats on Monday February 06, 2017 @04:04PM (#13583917)
Rust needs a Rust book not written by the Rust developers. "Rust for Dummies", if you will.
Re:Rust's 2017 Roadmap by kibwen on Monday February 06, 2017 @05:54PM (#13585099)
Then see O'Reilly's upcoming "Programming Rust" by Jim Blandy, who, despite working at Mozilla, has never been involved in Rust development, and has long years of experience developing SpiderMonkey, GDB, SVN, GNU Guile, and Emacs. It's still in early access, but 17 out of 20 chapters are available.

http://shop.oreilly.com/product/0636920040385.do

Re:Rust's 2017 Roadmap by stusmall on Monday February 06, 2017 @06:07PM (#13585194)
I've been getting early release PDFs of this book for a while now. I highly suggest it for moving from beginner to getting serious. I still think the Rust book is a better first read, but this is much more in depth and detailed.

One of the sections that was most useful to me was comparing how memory is laid out in a few different languages with a few different concrete code examples. These comparisons really helped me "get" borrowing.

Re:Rust's 2017 Roadmap by anamoulous on Monday February 06, 2017 @07:18PM (#13585743)
Did you pre-order the print book? Does that get you early access PDFs? Or does O'Reilly charge separately for the PDF and print?
Re:Rust's 2017 Roadmap by stusmall on Monday February 06, 2017 @08:02PM (#13586006)
I didn't pre-order the print, I just ordered the PDF version. If I remember correctly the print order didn't come with the PDF, but you get a discount if you get both. I'd check the site for details since this was getting on a year ago and my memory is poor.
Re:Rust's 2017 Roadmap by lsllc on Tuesday February 07, 2017 @10:25AM (#13589911)
Annoyingly, O'Reilly doesn't do a bundle. In the end, I found a 40% discount code and bought both.
Re:Rust's 2017 Roadmap by lsllc on Tuesday February 07, 2017 @10:25AM (#13589914)
I'll second that recommendation.
Re:Rust's 2017 Roadmap by dbaupp on Monday February 06, 2017 @05:07PM (#13584698)
Why couldn't Rust's developers write "Rust for Dummies"? I feel like you're connecting dots that aren't actually connected. Obviously having more books from different authors/perspectives is great for Rust, but I don't see, prima facie, why a non-Rust-developer author would do a better job of "Rust for Dummies" than a Rust developer.

For one, I would be surprised if a non-"expert" (which is, I presume, why you're so dismissive of Rust developers) could write a book that gives an accurate/useful mental model of Rust: teaching is the true test of one's knowledge about anything. Additionally, people paid to work on Rust and on Rust documentation/teaching materials (i.e. "Rust developers") are the people most regularly interacting with all sorts of beginners, and thus are likely to have great insight into, for instance, the common difficulties people hit, rather than just anecdoata about their own personal experience/background (which is good too, but is only one point of reference for things that people find hard).

Rust developers can write beginners books (indeed, the Rust book is designed to be this, and the second edition succeeds better the first, I've heard) just as much as non-Rust-developers can write expert books.

Re:Rust's 2017 Roadmap by tormeh on Monday February 06, 2017 @05:23PM (#13584839)
You're usually best able to explain something just after you learned it yourself. After a while you forget what was difficult about the thing you learned.

A C programmer, a Python programmer and a Java programmer should write the book together, with expert insight from a Rust pro.

Re:Rust's 2017 Roadmap by dbaupp on Monday February 06, 2017 @06:54PM (#13585575)
I'm not sure I agree with the anecdote in your first paragraph, and indeed I preemptively addressed it in my comment: one's own experience is just one way in which something can be hard to learn, whereas people who are regularly teaching and interacting with beginners have a broader view on what people find hard. My experience is, broadly speaking, good teachers are those that have had a lot of practice teaching their material.
Re:Rust's 2017 Roadmap by curun1r on Tuesday February 07, 2017 @11:13AM (#13590306)
It's probably a "forrest for the trees" problem...the developers of a language will have their perspective colored by low-level implementation details.

As an example, I found the explanation of trait objects incredibly confusing when I read the book. They confused the subject by immediately talking about static vs dynamic dispatch of functions, which is really an implementation detail and performance consequence of using them and not a part of what they are logically. An outsider might have started with a simple explanation of what a trait object is (an instance of a trait where the compiler cannot determine the concrete type at compile time) and make that clear before diving into the consequences of choosing to use one in your code.

Re:Rust's 2017 Roadmap by dbaupp on Tuesday February 07, 2017 @01:46PM (#13591536)
The Rust team is lucky enough to have a dedicated person (Steve Klabnik) writing documentation and teaching, who, as previously mentioned, gets to see a lot of the ways in which people struggle to learn Rust and practice different approaches for teaching it. For the most part, the dark corners of the language implementation are filtered from the compiler hackers, through Steve and his experience, into the actual user-facing documentation.

I think the specific case you mention was a problem more caused by a desire to have some documentation for 1.0, even if it isn't perfect, rather than just leaving the feature undocumented. That page is originally[1] based on a blog post[2] that is targeting people who want to know how they work internally, and there wasn't much time before 1.0 for feedback, revision and iteration of it (there was one cycle, which improved it in the direction you want, but more is always better). The second edition[3] doesn't have the 1.0 crunch date, and benefits a lot from feedback on the existing teaching material (like yours here) and the extra experience the team has had teaching Rust, so, by all reports, does a much better job. (It doesn't seem to currently have anything about trait objects, but I'm sure it will soon.)

[1]: https://github.com/rust-lang/rust/commit/dbccd70a5736fd2e898...

[2]: http://huonw.github.io/blog/2015/01/peeking-inside-trait-obj...

[3]: http://rust-lang.github.io/book/

Re:Rust's 2017 Roadmap by steveklabnik on Tuesday February 07, 2017 @02:25PM (#13591874)
Yes, this is true.

(And the second edition will have trait objects in it, it's not there yet though.)

Re:Rust's 2017 Roadmap by iopq on Tuesday February 07, 2017 @03:02AM (#13587878)
Just look at K&R. It's so... bland and boring. As a 13-year-old I couldn't keep reading it.
Re:Rust's 2017 Roadmap by CalChris on Monday February 06, 2017 @06:51PM (#13585554)
Re:Rust's 2017 Roadmap by gcp on Monday February 06, 2017 @04:09PM (#13583976)
There's several external books. I started from this one (via Safari):

https://www.amazon.com/Programming-Rust-Fast-Systems-Develop...

Re:Rust's 2017 Roadmap by Animats on Monday February 06, 2017 @04:21PM (#13584141)
"This title has not yet been released."
Re:Rust's 2017 Roadmap by gcp on Monday February 06, 2017 @04:24PM (#13584195)
You can get early access to it via various places, e.g. http://shop.oreilly.com/product/0636920040385.do
Re:Rust's 2017 Roadmap by steveklabnik on Monday February 06, 2017 @04:07PM (#13583959)
There are multiple already, including an in-progress one by O' Reilly. I've also heard rumors of another one getting started as well.
Re:Rust's 2017 Roadmap by leshow on Monday February 06, 2017 @04:12PM (#13584013)
Oreilly has an early release available: http://shop.oreilly.com/product/0636920040385.do

I have purchased it and it's pretty good. Although it really seems to be geared more towards experienced systems programmers. The online book is much better for beginners, IMO.

Re:Rust's 2017 Roadmap by AsyncAwait on Monday February 06, 2017 @04:49PM (#13584486)
The online book is undergoing a rewrite at http://rust-lang.github.io/book/ and will be published in print as well, it is unrelated to the book you linked, (but that book is also great).
Re:Rust's 2017 Roadmap by ice109 on Monday February 06, 2017 @04:49PM (#13584482)
I don't agree. the O'Reilly book is much gentler and pedagogically sound. many things in the online book are discussed before being introduced. not so in the O'Reilly book.
Re:Rust's 2017 Roadmap by nitrogen on Monday February 06, 2017 @05:20PM (#13584802)
I find that I learn better and trust the resource more if earlier lessons have hooks for later topics. It helps my mind piece everything together. But to each their own.
Re:Rust's 2017 Roadmap by steveklabnik on Monday February 06, 2017 @05:23PM (#13584843)
In this case, it wasn't so much "deliberate hooks" as it is "I took a lot of care to not do this, but then when pull requests came in to add things that were left out, sometimes they introduced forward references that we didn't realize at the time."
Re:Rust's 2017 Roadmap by nitrogen on Monday February 06, 2017 @07:22PM (#13585762)
Makes sense. I'll have to go through the rewritten parts again, as I'm having a heck of a time trying to pass the TcpStream object from Tokio into my actual service, as part of a personal learning exercise (https://github.com/mike-bourgeous/cliserver_rust/issues/6). I haven't broken down and asked online yet, partly out of sheer determination and partly because I'm in the middle of looking for a new place.
Re:Rust's 2017 Roadmap by steveklabnik on Monday February 06, 2017 @04:04PM (#13583904)
It will be printed by No Starch.
Re:Rust's 2017 Roadmap by adamnemecek on Monday February 06, 2017 @04:05PM (#13583927)
Lol, you guys are way ahead of me. And nostarch too.