Camp 1 · Schritt 1 von 12
Why Go?
Google's deliberately small language — and why it runs most of the modern cloud.
In 2007, three Google engineers (including Unix legends Ken Thompson and Rob Pike) got tired of waiting 45 minutes for C++ to compile. They designed Go: a language you can learn in a weekend that compiles in a blink and runs at near-C speed.
Small on purpose
Most languages accumulate features for decades. Go famously refuses them. It has:
- 25 keywords (Java has ~50, C++ far more)
- One loop (
for— no while, no do-while) - One obvious way to format code (
gofmt— ending style debates forever)
The payoff: any Go programmer can read any Go codebase. In team software, that's worth more than cleverness.
Why the cloud chose Go
Compiled, fast, tiny single-binary deployments, and concurrency built into the language (goroutines — a later camp!). The result: the modern infrastructure stack is substantially Go —
- Docker and Kubernetes — the containers running the internet
- Terraform, Prometheus, etcd — infrastructure tooling
- Backends at Google, Uber, Twitch, Cloudflare
A first taste
Clean, minimal, curly-braced. Notice fmt.Println — capital P — Go's
capitalization actually means something, which you'll see soon.
Which of these is a real Go design decision?
What's next
Run and dissect Hello World — packages, imports, and func main.