Then I guess the OP had another definition of "book" in mind. However, I'll say this: if Jim wants to write a complete book on Rust, I'd love to buy it. I'm more than halfway through his report and it has exactly the tone that I'm looking for in a programming book: clear, logical progression, to the point and no excessive humour that some books suffer from (I'm reading a book on Go (the game) at the moment and every paragraph contains a self-deprecating joke. It gets old after 2 or 3.)