6 ms·
> 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 alread
by adamnemecek 10y ago
> 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.
- steveklabnik 10y agoIt will be printed by No Starch.
- adamnemecek 10y agoLol, you guys are way ahead of me. And nostarch too.
- aturon 10y agoThe new book will be published by NoStarch press!
- Animats 10y agoRust needs a Rust book not written by the Rust developers. "Rust for Dummies", if you will.
- steveklabnik 10y agoThere are multiple already, including an in-progress one by O' Reilly. I've also heard rumors of another one getting started as well.
- gcp 10y agoThere's several external books. I started from this one (via Safari): https://www.amazon.com/Programming-Rust-Fast-Systems-Development/dp/1491927283/ref=sr_1_1?ie=UTF8&qid=1486415295&sr=8-1&keywords=programming+rust https://www.amazon.com/Programming-Rust-Fast-Systems-Develop...
- dbaupp 10y agoWhy 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.
- tormeh 10y agoYou'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.
- dbaupp 10y agoI'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.
- iopq 10y agoJust look at K&R. It's so... bland and boring. As a 13-year-old I couldn't keep reading it.
- kibwen 10y agoThen 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 http://shop.oreilly.com/product/0636920040385.do
- stusmall 10y agoI'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.
- anamoulous 10y agoDid you pre-order the print book? Does that get you early access PDFs? Or does O'Reilly charge separately for the PDF and print?
- stusmall 10y agoI 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.
- lsllc 10y agoAnnoyingly, O'Reilly doesn't do a bundle. In the end, I found a 40% discount code and bought both.
- lsllc 10y agoI'll second that recommendation.
- CalChris 10y agoRust Essentials is pretty good. https://www.packtpub.com/application-development/rust-essentials https://www.packtpub.com/application-development/rust-essent...
- leshow 10y agoOreilly has an early release available: http://shop.oreilly.com/product/0636920040385.do 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.
- ice109 10y agoI 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.
- nitrogen 10y agoI 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.
- steveklabnik 10y agoIn 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."
- nitrogen 10y agoMakes 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 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.
- AsyncAwait 10y ago
- deleted 10y ago[deleted]