# Python, JavaScript, Go & Rust - Explained Like a Human

You've probably stood at this fork: a dozen languages, every one with a loud fan club, every tutorial
insisting *theirs* is the one true path. So you freeze. Or you pick the one your bootcamp used and quietly
wonder if you backed the wrong horse.

Here's the calm truth: languages aren't a ranking. They're tools shaped by the problems their makers cared
about. Python feels nothing like Rust because they were built for different days at work. Once you can see
the *axes* a language sits on - how it handles types, how it runs, how it deals with memory, and where it
lives - the four in this guide stop looking like rivals and start looking like points on a map, and choosing
gets a lot easier.

This guide won't sell you a favorite. It'll give you the map.

## How to read this

- **Want to choose right now?** Skip to [Phase 3: How to Choose](03-how-to-choose.md) - there's a
  comparison table and a decision walkthrough at the top.
- **Want it to finally make sense?** Read in order. Phase 1 builds the mental model; Phase 2 places each
  language on it; Phase 3 turns that into a decision.

## The phases

1. **[What Actually Makes Languages Different](01-what-makes-languages-different.md)** - the handful of axes
   that matter (typed vs dynamic, compiled vs interpreted, how memory is managed, and where the language
   runs), so the four aren't random names but points on a map.
2. **[The Four, Plainly](02-the-four-plainly.md)** - one fair section each for Python, JavaScript/Node,
   Go, and Rust: what it's for, a tiny taste of how it reads, and the real trade-offs - no fanboyism.
3. **[How to Choose](03-how-to-choose.md)** - a practical, judgment-flagged way to pick by what you're
   building and the people around you, with a side-by-side table and the reassurance that your first
   language matters less than the internet makes you think.

> This guide is about choosing and feeling the difference. The deeper *why* behind these axes lives in
> sibling guides - what happens when code runs, and how memory and garbage collection work - linked
> throughout. We point you there rather than re-teaching it here.