Then I guess the OP had another definition of &quot;book&quot; in mind.  However, I&#x27;ll say this: if Jim wants to write a complete book on Rust, I&#x27;d love to buy it.  I&#x27;m more than halfway through his report and it has <i>exactly</i> the tone that I&#x27;m looking for in a programming book: clear, logical progression, to the point and no excessive humour that some books suffer from (I&#x27;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.)