Why Rust’s Documentation is on My Suggested Reading List


If you haven’t read the Rust Book from the Rust website, please go do so now. Including a docs website on my reading list was kind of a weird decision. For the most part documentation is dry and usually for people who know what they are looking for, the concepts behind the documentation are usually left to the third party tutorial makers(with some notable exceptions). But the Rust Docs are completely different.

Not only are they verbose and informative, they’re downright educational. The writers of the rust documentation book, assume that the reader doesn’t understand the nuanced lower level concepts in programming(ie. me). And then take the time to explain them. The chapter on Ownership is fantastic and explains the pitfalls of other languages when it comes to memory safety and how rust builds in some safety features to prevent them.

This should be unsurprising to those who understand the reasoning behind the creation of a language like Rust. It was entirely designed to be performant, safe, and secure. This means that a lot of modern programs that have vulnerabilities can be rewritten in rust without those vulnerabilities and without having to think about it.

If you’re interested in Rust then you should absolutely checkout its documentation that walks you through from hello world to a production ready web server. For those who already know Rust, you should absolutely checkout Redox a simple OS built with Rust.

Leave a Reply

Your email address will not be published. Required fields are marked *