PKUFlyingPig/cs-self-learning
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
PKUFlyingPig/cs-self-learning
PKUFlyingPig/cs-self-learning is a highly starred, actively maintained Chinese computer science self-study guide published as a documentation site at csdiy.wiki. It collects curated open courses, books, and learning paths, with an English version and explicit contribution workflow for adding or updating course pages.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Choose this fork only if you specifically want its early custom additions and are comfortable owning maintenance. For most adopters, upstream is the better base because it is actively maintained, much more complete, and far less risky to extend.
For most adopters, upstream is the better choice. This fork adds no visible value, is 94 commits behind, and appears stale, so it is only sensible if you want a frozen snapshot for historical reference or private experimentation.
Prefer upstream if you want current content and ongoing maintenance. Prefer this fork only if you specifically want the CSAPP lab-code addition and are comfortable with an older, lightly maintained snapshot.
Choose upstream unless you specifically need this fork’s Vim English edits; the fork is too stale for general adoption and looks useful mainly as a small localized content variant.
Choose this fork only if you specifically want its older, simplified, community-comment-oriented variant. For most adopters, upstream is the better base because it is actively maintained, bilingual, and much more current.
Choose the upstream unless you specifically want a frozen, minimally changed copy. This fork adds no visible functionality and is materially behind on content maintenance.
Prefer upstream for normal use. This fork has no visible fork-specific improvements and is 61 commits behind, so it is best treated as a stale snapshot rather than an adoption candidate.
Prefer upstream unless you specifically need an unmaintained snapshot; this fork offers no added capabilities and is substantially behind on content and upkeep.
Prefer upstream unless you explicitly need an older, frozen version; this fork adds no visible capabilities and is materially behind on content maintenance.