Comprehensive Rust: Google's Classroom Course for Teaching Rust to Experienced Engineers
This is the Rust course used by the Android team at Google. It provides you the material to quickly teach Rust.
At a glance
- What is it?
- Comprehensive Rust is Google's multi-day Rust course, built for classroom teaching and aimed at engineers with C++ or Java backgrounds. This review covers its structure, tooling, and why it is not designed for solo self-study.
- Who is it for?
- Adopt Comprehensive Rust if you are an experienced engineer, especially with a C++ or Java background, and you plan to teach Rust in a live classroom setting. It is also a solid base for university courses, as shown by the 5-day class built on it.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 12 days ago.
- What is it written in?
- Mainly Rust, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- google/comprehensive-rust33,525 ★ · +211
| Repository | 2026-08-18 | 2026-11-15 |
|---|---|---|
| google/comprehensive-rust | 33.3k | 33.5k |
211 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What Comprehensive Rust Actually Is
The course covers Rust from basic syntax to generics and error handling, and it includes deep dives into Android, Chromium, bare-metal, and concurrency. Those deep dives are what separate it from generic Rust tutorials. They target specific domains where Rust is being adopted in industry. The Android and Chromium sections reflect Google's own use cases, which gives the material a practical edge that many other courses lack. The bare-metal and concurrency sections are more specialized, so they may not fit every team.
The Classroom Mechanism: Why Live Teaching Is Core
The reliance on live interaction is a genuine constraint. If you are a solo learner, you will not get the same value. The course material alone cannot replicate the back-and-forth of a classroom. This is a deliberate trade-off, and the project acknowledges it openly. For teams, that means you need a qualified instructor, not just a copy of the repository. The instructor must be comfortable with Rust and able to improvise around the code samples.
Getting It Running: Toolchain and Commands
To build the course locally, you need Rust, Bazel, and mdbook, plus several mdbook plugins. The README gives exact setup steps. First, install Rust via rustup.rs. Then install Bazel via Bazelisk. Clone the repository and run `cargo xtask install-tools` to install all required tools, which land in `~/.cargo/bin/`. The project uses a custom xtask command runner, so you do not need to manage each tool manually. The key commands are `cargo xtask serve` to start a web server on http://localhost:3000, `cargo xtask rust-tests` to test the included Rust snippets, `cargo xtask web-tests` for web driver tests, and `cargo xtask build` to generate a static version in the `book/` directory. For translated versions, you add a language flag, for example `cargo xtask serve -l da` for Danish. On Windows, you must enable symlinks with `git config --global core.symlinks true` and enable Developer Mode. The toolchain is heavier than a typical static site generator, but it is automated through xtask, which reduces manual setup errors.
The Translation and Localization Pipeline
The course has a serious translation infrastructure. The README mentions mdbook-i18n-helpers and i18n-report as part of the build tools, and the commands support language flags for serving and building translated versions. This is not a one-off localization; it is a structured pipeline that likely uses gettext-style PO files, though the README does not detail the exact workflow. The existence of TRANSLATIONS.md suggests there is a documented process for adding new languages. For a team that needs Rust training in multiple languages, this is a significant advantage. The i18n tooling adds complexity to the build, but it is a deliberate investment in making the course usable beyond English-speaking teams.
Limitations and Failure Modes
There is also a maintenance cost. The course is actively developed, with the last push on 2026-10-02, but that means the content changes. If you fork it or build your own course on top of it, you will need to track upstream changes. The Apache-2.0 license allows modification, but you have to keep the license notice. The repository has no GitHub releases. Teams that adopt it should plan to monitor the upstream repository for changes.
Alternatives and How They Differ
There is also the option of using the course as a base and adapting it, which is what the 5-day university class did. That is a legitimate approach, but it requires the same instructor expertise. The Apache-2.0 license permits it. You would need to manage your own fork and keep it in sync with upstream, which is a real cost.
Maintenance and License Implications
The course includes web driver tests and Rust snippet tests, which are a quality safeguard. The `cargo xtask rust-tests` command tests the included Rust snippets, and `cargo xtask web-tests` runs web driver tests. The Cargo workspace lists many chapter crates, so the snippets are tested rather than only rendered. However, maintaining those tests is part of the upkeep. If you customize the course, you should also update the tests, or you risk breaking the build. The README points to CONTRIBUTING.md for contribution guidelines.
Editorial conclusion
Adopt Comprehensive Rust if you are an experienced engineer, especially with a C++ or Java background, and you plan to teach Rust in a live classroom setting. It is also a solid base for university courses, as shown by the 5-day class built on it. Do not adopt it for self-study: the README explicitly warns that you would miss classroom discussions, Q&A, and the compiler errors triggered during live demos. Before using it, verify that your team can commit to the full multi-day format and that you have a teacher comfortable with Rust. Also check the current state of speaker notes and videos, since the README lists them as planned improvements. The course is Apache-2.0 licensed, so you can adapt it, but you must keep the license notice. If you need a self-paced tutorial, look elsewhere; this is a teaching aid, not a solo learning path.
Frequently asked questions
comprehensive rust vs rust book
The README positions this as a multi-day course developed by Google's Android team for teaching experienced engineers, typically with a C++ or Java background. It says the format is less ideal for self-study because you would miss the classroom discussions, the questions and answers, and the compiler errors triggered while going through the samples.
Is Rust basically C++?
The repository does not compare the languages. It says the course is used to teach experienced software engineers who typically have a background in C++ or Java, and it includes deep dives on Android and Chromium plus a bare-metal chapter with compiled examples.
How do I build and serve the Comprehensive Rust course locally?
Install Rust, then Bazel through the Bazelisk version manager, then clone the repository, then run `cargo xtask install-tools` to install the correct versions of the documentation tools. After that `cargo xtask serve` starts a web server on port 3000, and `cargo xtask build` produces a static version in the book directory. Run `cargo xtask` on its own to see every command.
How are the code samples in Comprehensive Rust verified?
Many chapters are Cargo workspace members, so the snippets in the text are compiled rather than merely rendered, and one test command tests the included Rust snippets. A second command runs web driver tests in a tests directory. On Windows, symlinks and Developer Mode have to be enabled first or the checkout will not reproduce the tree.
What languages is the Comprehensive Rust course available in?
It has translations, and the build tooling is built for them: a language flag on both the serve and build commands taking an ISO 639 code, a Danish example in the readme, internationalisation helpers and a reporting tool in the tool list, and a separate translations document with further instructions. The build step also notes that exercises have to be built and zipped separately and added into the output by hand.
Official sources
Where developers are discussing it
Posts on Hacker News, dev.to and Lobsters that link to this repository, found by our scan of those communities. 1 in the last 30 days; newest first.
- State of AI Instruction Quality: Coding Agent Comparisondev.to · Oct 21, 2026 · 6 points · 0 comments
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/google-comprehensive-rust)Star history chart for your README
[](https://hysenlabs.com/projects/google-comprehensive-rust)Was this useful?