The Rust course is free to read and closed to repackaging

No License is a deliberate choice that blocks repackaging

The licensing section is the most consequential paragraph in this repository, and it is short. In choosing an open source licence the project selected No License, which it links to the choosealicense.com entry for no permission. The stated effect is that readers may fork and read freely, but may not privately modify the text and then redistribute it. Anyone who needs that is asked to make contact first.

That is an unusual position for something described as an open source tutorial, and it is worth being precise about what it does and does not do. It is not a copyleft licence, so there is no source disclosure obligation attached to a derivative. It is closer to a claim of permission over redistribution, granted for reading and forking alone. The repository metadata carries no SPDX licence identifier at all, which is consistent with a project that deliberately declined to adopt one of the standard licences.

The reason given for the whole book being free rather than sold is separate from the licence, and it is stated plainly in the author's own notes on writing it.

Reading, practice and an AI news feed are three separate sites

Three destinations are listed, and they are not stages of one course. Online reading is at course.rs, which is also the homepage the project publishes. Online practice is at practice.course.rs, a separate host, so the exercises are not embedded in the reading site. A third address, beatai.org, is described as AI frontier learning and as a daily selection of good writing from around the world, live and high quality.

That third entry has nothing to do with Rust specifically, and it is the point where the repository stops being a single subject. Reading and practice form a coherent pair for one language. A daily curated feed is a different product with a different audience, and it shares a project page with the tutorial.

The stated purpose of the tutorial itself is narrow and specific: it was made for users in China, covers entry for newcomers, and is meant to raise the productivity of people who already know Rust. It is not described as a general Rust reference.

The text credits three upstream books and follows their MIT terms

The book stands on existing documentation and says so rather than implying it was written from first principles. Three sources are named directly: the Rust Book at doc.rust-lang.org/book, the Rust nomicon at doc.rust-lang.org/nomicon, and Async Rust at the rust-lang async book. A longer list is kept separately in the repository at assets/writing-material/books.md.

The licensing reasoning follows from that. The project states that the great majority of the referenced books are offered under a dual Apache and MIT licence, and that because of this it chose to follow the MIT half of the pair. The credit is then given uniformly, with a note that all the borrowed books are listed together in one place.

This is worth noting for a reader checking provenance. A tutorial that borrows from the official Rust Book is downstream of it, so corrections to the upstream text do not automatically appear here, and the project is candid that the material is acknowledged rather than original.

170 chapters and 1.1 million characters, all written by hand

The author's account of the effort gives three numbers: more than 170 chapters, more than 1.1 million Chinese characters, and more than 800 hours of work. The claim attached to them is that every chapter was written by hand with no compromise on quality, and that readers who have used the text would recognise that.

Those figures are self reported, and the character count is a measure of volume rather than of coverage. What they do establish is the shape of the project: this is a book length work, not a tutorial with a defined endpoint. A reader budgeting time should treat 170 chapters as the unit of commitment rather than assuming a weekend.

The author also addresses the obvious commercial question directly, noting that a reader asked why the book is open source rather than published. The answer given is that for Rust to take hold in China, someone has to do the work without compensation, and the hope is to contribute a small part of it. The same passage concedes that seeing a star on the project also makes the author happy.

The repository is a book source tree, not a code project

What sits in the repository explains why the primary language is recorded as Rust even though there is no Rust crate here. The tree is a book layout: a TOML configuration file at the root named book.toml, a src/ directory holding the text, a theme/ directory, and an assets/ directory for images. Alongside those are genpdf.sh and deploy.sh, plus a ci/ directory and a .github/ directory.

Two scripts, one for generating a PDF and one for deploying, indicate that the online text is produced from this same source rather than maintained separately on the web. The repository’s genpdf.sh identifies the project as an mdBook book, installs mdbook and mdbook-pdf, and runs mdbook build to generate its PDF.

There are no GitHub releases. Whatever you read at course.rs is the state of the source tree, and there is no changelog to tell you what changed between one visit and the next.

Six contributors are named, and there are 20 open issues

The contributors section thanks everyone who has contributed and then singles out six accounts by name: EluvK and AllanDowney, followed by SUN-LG, JesseAtSZ, Rustln and 1132719438. One of those (SUN-LG) is displayed with a Chinese name, 孙立刚, and the rest as GitHub handles.

The project has 31095 stars and 2601 forks, with 20 open issues, and the last push to the default branch is dated 2026-10-30.

None of this says the project is finished or paused. It is not archived, and there is no stated maintenance policy in the repository.

Editorial conclusion

This course fits a reader who reads Chinese, wants one structured text rather than scattered documentation, and is willing to work through a long book. Check two things first. The language of instruction is Chinese, with no English edition named in the repository. And the licence is No License, which permits forking and reading but explicitly forbids privately modifying the text and redistributing it, so if your need is a translated or packaged derivative you have to contact the maintainer before building it.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. sunface/rust-course on GitHub