Why You Should NOT Learn Rust!

Main ideas / concepts (5 reasons)

1. Rust may not maximize your odds of getting a programming job

   • There are Rust jobs, but overall demand is relatively low.
   • Existing roles tend to require high expertise.
   • If your primary goal is to find a job quickly/easily, the speaker suggests considering languages with higher demand, specifically: C++ , C# , Java.
   • Caveat: Rust is newer; as popularity grows, more Rust-specific jobs should appear.
   • Alternative approach:
     • Learn Rust via tutorials and side projects to get ahead of the curve, or
     • Use Rust in your current workplace when it’s needed for a technical challenge or for building internal tools (e.g., CLI apps).

2. Rust may be the wrong tool if efficiency/correctness aren’t critical

   • Rust supports building software that is highly efficient and correct.
   • If those qualities aren’t essential, you might choose something else.
   • The speaker addresses an argument that “all software should be efficient and correct,” but clarifies there’s a different threshold depending on the application:
     • Embedded medical devices: prioritize correctness and efficiency (even if it takes longer).
     • Social media / web apps: may accept trade-offs for faster time-to-market.
   • Caution example: Rebuilding a whole web app in Rust + WebAssembly requires considering trade-offs.
   • Caveat: If you’re learning, it’s okay to use Rust even if it doesn’t make business sense.

3. Rust shouldn’t be your first programming language (in general)

   • The speaker recommends not learning Rust as a first language unless you specifically want that path.
   • They suggest starting with something that may be easier to learn, even if “less efficient/powerful,” such as:
     • JavaScript or Go.
   • Exception (caveat): If you want to do systems / low-level programming, Rust can be reasonable as a first language.

4. Rust may not fit you if you have “shiny object syndrome”

   • The speaker warns against treating Rust as something you can pick up quickly and then move on.
   • Rust has a learning curve and requires dedication to become proficient.
   • They acknowledge resources can help (example mentioned: a “Rust book” and “this YouTube channel”).

5. Rust may not be for you if you currently program in Go

   • The speaker jokes about excluding Go developers (“don’t allow go developers into the rust gang”), presenting it as a tongue-in-cheek reason.
   • They also state they struggled to find a truly legitimate fifth reason, implying it’s mostly humor.

---

Methodology / instructions mentioned (practical guidance)

• If job-focused:

  • Prefer a higher-demand language (C++ / C# / Java) to improve hiring odds.
  • Optionally: learn Rust anyway to prepare for future demand via tutorials or side projects.

• If using Rust in real work:

  • Look for tasks where a technical challenge calls for an efficient/correct language.
  • Advocate for Rust to build internal tooling, such as CLI apps.

• If learning for personal growth:

  • Use Rust even if it isn’t the “best business tool” for the situation.

• If choosing a first language:

  • Generally start with JavaScript or Go, unless your goal is systems/low-level programming.

• If you struggle with focus/excitement cycles:

  • Avoid Rust if you tend to chase new technologies without sticking with them long enough to build proficiency.

• If you currently use Go:

  • The speaker frames Rust adoption as an off-beat challenge (jokingly).

---

Speakers / sources featured

• Speaker: Bogdan (host of the channel)
• Sources mentioned (not as featured speakers):
  • “The Rust book”
  • “This YouTube channel” (as a learning resource)
  • A “Rust cheat sheet” referenced in the description/link (no other named creator)