0.2 The series: OS → networking → security → HTTPS → Go → C → Rust

This guide belongs to one course, read in this order:

   1  OS & Linux  ──▶  2  Networking  ──▶  3  Security  ──▶  4  HTTPS walkthrough
                         2a OSI map          3a From Zero        (one request through
                         2b TCP/IP           3b In Depth          every guide)
   ════════════════  Go and Rust, alongside every step  ════════════════

   Languages track:   Go  ──▶  C  ──▶  Rust  (you are here)
                      GC +     the       C's control, with the
                      runtime  machine   discipline checked by the compiler

Why Rust comes last in the languages track. Rust's rules make the most sense once you have seen both alternatives fail. In C you have seen a use-after-free, a double free, and a data race. In Go you have seen GC pauses, nil-pointer panics, and the slice aliasing bug in Go §6.6. After that, the borrow checker stops looking like an obstacle. It is the C guide's ownership discipline, written down as rules and enforced at compile time.

Reading paths:

• From Go (backend engineer): Part 0 → Ch 1–12 (slowly, especially 6–8) → 16–22 → 28–31 → 47–48 → 62 → 68.
• From C (systems / embedded): Part 0 → Ch 1, 6–10 → 16–19 → 22 → 28–29 → 33–34 → Part IV → 57–61.
• Security engineer: Ch 1, 6–10 → 33 → Part VI → 49–50 → 55.
• SRE / platform: Ch 1–12 → 24 → 30–31 → Part IV → 47 → 65–67.