sunface/rust-course: a Chinese Rust textbook with an explicit non-distribution licence

What problem a Chinese-language Rust book actually solves

Most Rust learning material is written in English, and the borrow checker is hard enough without also translating the explanation in your head. This project exists to remove that second step for Chinese-speaking readers. The README frames the audience as 新手入门, 老手提升生产力: newcomers on one side, working developers who want to raise output on the other. That is a wider span than a typical tutorial, and it is the reason the book runs to 170-plus chapters and, by the author's own count, more than 1.1 million characters written over 800-plus hours. The author states that every chapter is handwritten and that quality was not traded away, which is a claim about process rather than a measurable property. Read it as intent, not evidence. The concrete thing the repository gives you is a structured Chinese curriculum with a companion practice site at practice.course.rs, separate from the reading site at course.rs. If your team reads English comfortably, the problem this solves largely disappears, and you should weigh that honestly before adopting it.

Reading site, practice site, and repository as three separate artifacts

The repository is the source of the text. The README points readers to course.rs for online reading and to practice.course.rs for exercises, and it also links beatai.org as a separate AI-focused reading feed. Those are three different destinations with different maintenance stories. The repository itself is a book project: the README shows a banner image, a contributor table, and a section on borrowed material, which is the layout of a manuscript repository rather than a library. There is no crate to install, no binary to run, and no API to call. That matters when you evaluate it, because the usual questions about dependency churn, semver and runtime risk do not apply. What applies instead is editorial drift: whether the prose keeps pace with Rust itself, and whether the exercise site stays aligned with the chapters. The repository topics list includes deno, javascript and wasm alongside rust-book and rust-learning, which suggests the material reaches into tooling around Rust rather than staying inside the language. The README does not describe that coverage in detail, so treat the topic list as a hint about scope, not a table of contents.

Getting the material onto a local machine

The README does not provide a build command, a package manifest, or a documented toolchain for rendering the book locally. What it does give is the canonical reading path: open https://course.rs for the text and https://practice.course.rs for exercises. For a local copy, the only operation the README explicitly sanctions is forking the repository and reading it, which is a git-level action rather than a build. If you want a pinned snapshot for an offline cohort, a git clone followed by a checkout of a specific commit is the mechanism the repository layout supports, and the default branch is main. Beyond that, anything about how the source files are converted into the published site would be speculation on my part, because the supplied material does not describe a build pipeline, a static site generator config, or a deployment step. If local rendering matters to your use case, that is a gap you need to close by inspecting the repository tree yourself, not by trusting a review.

The licence is the first thing to resolve, not the last

The README is unusually direct here. It states that the project chose No License, linking to choosealicense.com/no-permission/, and explains the intent: readers may freely fork and read, but may not privately modify and then repackage and distribute. That is a permission statement written in prose, and it is narrower than any standard open source licence. The same README then describes the borrowed sources, including the Rust Book, the Rust nomicon and Async Rust, and says that because those are largely dual-licensed under Apache and MIT, this project chose to follow the MIT terms from among them, with a consolidated acknowledgement. Those two statements sit next to each other and pull in different directions. One says no licence is granted over this work. The other says MIT terms were adopted for the borrowed material. A reader cannot resolve that tension from the README alone, and I am not going to pretend otherwise. For an individual learner this is mostly academic. For a company that wants to mirror chapters into onboarding docs, translate them, or ship them inside a paid course, it is the deciding factor, and the correct next step is to contact the maintainers as the README itself invites.

Where this book is the wrong tool

Two failure modes are visible from the material. The first is language fit. If your engineers read English without friction, the official Rust Book and the nomicon are the upstream sources this project itself credits, and going to them removes a translation layer and a third-party maintenance dependency at the same time. The second is verification. The README makes strong claims about depth and care, but it offers no errata process, no versioning scheme for the text, and no statement about which Rust edition the examples target. For a beginner following along, an example that no longer compiles is a hard stop, and there is nothing in the supplied material that tells you how quickly such issues get fixed. A third case is narrower: if you need a reference you can quote, excerpt or adapt in commercial training material, the No License statement is a direct blocker, and no amount of chapter depth compensates for that.

The Rust Book and the nomicon: what actually differs

The difference is not quality, it is position in the stack. The Rust Book is the official language introduction, maintained alongside the language itself, and it is one of the sources this project credits. The nomicon goes the other way, into unsafe Rust and the rules underneath the safe surface. rust-course sits between and around them: a single Chinese-language work that spans beginner material and productivity material for experienced developers, with a separate exercise site attached. So the choice is not which book is better. It is whether you want one continuous Chinese reference covering both ends, or two English references each doing one job with upstream authority. The trade is coverage and language against provenance and update cadence. The README's own acknowledgement section is the clearest evidence for how to think about it: this project stands on those upstream books, and it says so.

Maintenance cost and what the repository commits to

The README reports more than 800 hours of writing and a contributor list, which tells you the project has had sustained human input, but it makes no commitment about release cadence or long-term maintenance. There are no retrieved releases, so there is no version history to reason about. The last push date on the repository is recent, which indicates the project is active, but activity is not the same as a compatibility guarantee for the examples. Practically, the cost of depending on this book is the cost of re-reading a chapter when Rust changes and the text has not caught up. That cost is low for a reader and high for an organisation that has built a curriculum on top of it. If you are in the second group, pin a commit, keep a local copy, and track upstream changes yourself rather than assuming the published site reflects the edition you compile against.

Editorial conclusion

Adopt rust-course if your readers work in Chinese and you want a single deep reference rather than a translated English book. Do not fork it into an internal training product or repackage chapters: the README states No License, which permits forking and reading but not private modification followed by redistribution, and the borrowed-material section points to MIT terms for the upstream sources rather than granting rights over this compilation. Before using it, verify the licence status directly with the maintainers and check whether the chapter you need is prose only or has a matching exercise on practice.course.rs.

Official sources

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