I think the most important thing the Rust project can do to increase the use of the language is to make it easier to learn. And I think the way to do that is to provide a document that teaches how to use Rust in a way that avoids the difficult corners of the language that can be stumbled upon if you don’t know what you are doing, but are avoidable.

This is a bit like user-interface design – good UIs give you access to every aspect of the capability/service behind them, but the most oft-used, most important aspects of the service are front and center.

I don’t think the Rust Book accomplishes this, nor does Jim Blandy’s book (which I think is excellent in many ways). Both document a wide swath of the language, but don’t home in on a methodology that allows you to avoid lifetime hell or borrow-checker hell unnecessarily. I think experienced Rust programmers know how to do this and beginners don’t. I’m suggesting a document that captures what they’ve learned that allows them to co-exist with the Rust compiler and avail themselves of the advance that Rust represents over C and C++ without encountering avoidable problems.