4 ms·

They should put having technical books on Rust as a goal. I learn via technical books btw. Does anybody know if there's a rust book coming out? I mean Julia

They should put having technical books on Rust as a goal. I learn via technical books btw. Does anybody know if there's a rust book coming out? I mean Julia is having a book from Manning and they're not even version 1.

burntsushi 11y ago
There is an official book: https://doc.rust-lang.org/stable/book/ https://doc.rust-lang.org/stable/book/
aturon 11y ago
There's an O'Reilly book in the works: http://www.amazon.com/Programming-Rust-Jim-Blandy/dp/1491927283 http://www.amazon.com/Programming-Rust-Jim-Blandy/dp/1491927... And The Rust Programming Language (https://doc.rust-lang.org/book https://doc.rust-lang.org/book) is on its way to paper publication. The newly minted Rustonomicon (https://doc.rust-lang.org/nightly/nomicon/ https://doc.rust-lang.org/nightly/nomicon/) that covers deeper aspects of Rust is hopefully destined for the same.
- mrec 11y ago
  It's probably a niche interest, but do you know if anyone's working on a Rust equivalent of Stroustrup's Design and Evolution of C++? I found that book a huge help in grokking the "why"s behind the language, and gaining some degree of mechanical sympathy with it. I appreciate that the vast majority of Rust's D&E happened in the open, so most of it's probably still available, but it's been a long and twisty road since Graydon's initial public post and picking out a coherent narrative from umpteen separate slowly-linkrotting fora would be no small task.
  - steveklabnik 11y ago
    I dream of doing such a thing someday. I'm not aware of anyone that's actively working on it. I did a talk at FOSDEM 2015 along these lines, which apparently got lost with a lot of them :/
- DominikD 11y ago
  All of these are great (really, not being smug) but FWIW neither TRPL nor the Rustonomicon address my needs (Rust by example is probably the closest). It may be related to the weird set of skills and needs I have but hey, I'll post about my experience anyway in case someone shares my POV. ;) My background includes OS development (Windows COM), driver development (C for kernel mode driver and C for HW firmware development), web development (C#/ASP.NET and JavaScript - both in browser and Node.js), and most recently HW simulation using C++/SystemC. Mixed bag, I know. What I want to use Rust for is desktop app development. I could go C, but that's a lot of manual labor. I could go C# but I don't like paying cost of the runtime on desktop. I could go C++ but I don't like getting my soul crushed. I tested viability of Node (and Python, actually) for desktop apps but it just didn't fit my needs. So I want to love Rust. And I kinda do. Initially I didn't like certain things (bits of syntax mostly) but I've learned to love them. The problem is: none of the resources tell me interesting stuff all the way through the system. I feel like knowledge could be laid out with all the details from "this is syntax" to "this is what happens" to "this is what you can/cannot do" to "this is why this happens" to "this is what this means to the compiler" to "this is what happens under the hood/in asm". I'd also[1] love to have something that roughly maps rust to C and gives me clear explanation of pros/cons of various approaches. It wasn't immediately obvious to me if I can have static methods. Of whether it's important to have self mutable (or not) as a method param. Or how to organize structures now that I have to keep mutability in mind. I know this comes with time but I'd love a kick of sorts. :) Best ideas tend to come from reading existing pieces of code but rarely knows if author is worth mimicking. :S Either way - I'm invested and I like what I'm seeing. Great work guys! [1] or these could become one thing, dunno
  - Gankro 11y ago
    Fundamentally Rust just doesn't define things well enough to be able to answer the "this is what it compiles to" issue. There's some things like `Option<&T>` which we guarantee but really it's a lot of "man, if the compiler was smart enough...". Even then, a stray annotation can wall LLVM and kill any chances of perf (e.g. if the function is not a candidate for cross-crate inlining).
    - 11y ago
gbersac 11y ago
I have been one of the backers of this kickstarter project for a rust book : Rust Programming Concepts https://www.kickstarter.com/projects/1712125778/rust-programming-concepts-book?ref=nav_search https://www.kickstarter.com/projects/1712125778/rust-program...

burntsushi 11y ago

There is an official book: https://doc.rust-lang.org/stable/book/ https://doc.rust-lang.org/stable/book/

aturon 11y ago

There's an O'Reilly book in the works: http://www.amazon.com/Programming-Rust-Jim-Blandy/dp/1491927283 http://www.amazon.com/Programming-Rust-Jim-Blandy/dp/1491927... And The Rust Programming Language (https://doc.rust-lang.org/book https://doc.rust-lang.org/book) is on its way to paper publication. The newly minted Rustonomicon (https://doc.rust-lang.org/nightly/nomicon/ https://doc.rust-lang.org/nightly/nomicon/) that covers deeper aspects of Rust is hopefully destined for the same.

mrec 11y ago
It's probably a niche interest, but do you know if anyone's working on a Rust equivalent of Stroustrup's Design and Evolution of C++? I found that book a huge help in grokking the "why"s behind the language, and gaining some degree of mechanical sympathy with it. I appreciate that the vast majority of Rust's D&E happened in the open, so most of it's probably still available, but it's been a long and twisty road since Graydon's initial public post and picking out a coherent narrative from umpteen separate slowly-linkrotting fora would be no small task.
- steveklabnik 11y ago
  I dream of doing such a thing someday. I'm not aware of anyone that's actively working on it. I did a talk at FOSDEM 2015 along these lines, which apparently got lost with a lot of them :/
DominikD 11y ago
All of these are great (really, not being smug) but FWIW neither TRPL nor the Rustonomicon address my needs (Rust by example is probably the closest). It may be related to the weird set of skills and needs I have but hey, I'll post about my experience anyway in case someone shares my POV. ;) My background includes OS development (Windows COM), driver development (C for kernel mode driver and C for HW firmware development), web development (C#/ASP.NET and JavaScript - both in browser and Node.js), and most recently HW simulation using C++/SystemC. Mixed bag, I know. What I want to use Rust for is desktop app development. I could go C, but that's a lot of manual labor. I could go C# but I don't like paying cost of the runtime on desktop. I could go C++ but I don't like getting my soul crushed. I tested viability of Node (and Python, actually) for desktop apps but it just didn't fit my needs. So I want to love Rust. And I kinda do. Initially I didn't like certain things (bits of syntax mostly) but I've learned to love them. The problem is: none of the resources tell me interesting stuff all the way through the system. I feel like knowledge could be laid out with all the details from "this is syntax" to "this is what happens" to "this is what you can/cannot do" to "this is why this happens" to "this is what this means to the compiler" to "this is what happens under the hood/in asm". I'd also[1] love to have something that roughly maps rust to C and gives me clear explanation of pros/cons of various approaches. It wasn't immediately obvious to me if I can have static methods. Of whether it's important to have self mutable (or not) as a method param. Or how to organize structures now that I have to keep mutability in mind. I know this comes with time but I'd love a kick of sorts. :) Best ideas tend to come from reading existing pieces of code but rarely knows if author is worth mimicking. :S Either way - I'm invested and I like what I'm seeing. Great work guys! [1] or these could become one thing, dunno
- Gankro 11y ago
  Fundamentally Rust just doesn't define things well enough to be able to answer the "this is what it compiles to" issue. There's some things like `Option<&T>` which we guarantee but really it's a lot of "man, if the compiler was smart enough...". Even then, a stray annotation can wall LLVM and kill any chances of perf (e.g. if the function is not a candidate for cross-crate inlining).
  - 11y ago

gbersac 11y ago

I have been one of the backers of this kickstarter project for a rust book : Rust Programming Concepts https://www.kickstarter.com/projects/1712125778/rust-programming-concepts-book?ref=nav_search https://www.kickstarter.com/projects/1712125778/rust-program...