I want to see a 30 minute 'introduction to Rust.'
Do you know C++?
Assume that you know systems programming, but acknowledge it.
It's like static typing, for the language.
The one we have is bad.
A spec allows you to answer 'bug or not?'
Bonus points: executable
I want to see 'PEP' for Rust.
Specific, cross-cutting topics.
We have a really confusing 'tutorial' and then 'tutorials.'
More in-depth than the tutorial, but not exhaustive.
Guides are for best practices, common patterns, and use cases.
Esoterica belongs in the spec only!
Ideally, the guides would cross-reference the API tutorials.
Traits vs. Implementations?
Every function should have examples.
... sort of.
Documentation about the compiler itself.
"How to Contribute to Rust."
... basically, the wiki. Which is terrible.
Mean, but for your own good.
The biggest failure of our documentation today is the same failure most documentation written by programmers has.
Nobody cares about your weird edge cases.
Resisting the urge to add strange information is crucial. That's what the spec is for.
All documentation should be focused on how we're great.
Case study: Ruby on Rails
A vibrant blogging community leads to poor documentation.