A Tour of Go

Go's designers put the introduction to their own language in the browser, with a runnable playground on every page, and then kept it short. Four sections, each ending in exercises, and you can be writing goroutines the same afternoon you started. It runs offline too — install the tour binary and it serves locally, which is handy on a plane or behind a corporate proxy.

What it demonstrates as much as teaches is Go's smallness. There isn't much language here, and the tour finishes without you feeling short-changed, which says something about the design.

The four sections

• Basics — packages, variables and functions; flow control; then structs, slices and maps
• Methods and interfaces — the constructs that define objects and their behaviour, including the interface satisfaction rules that surprise people from other languages
• Generics — type parameters, with worked examples of when to reach for them
• Concurrency — goroutines, channels, select, and the patterns built from them

The exercises are the good part. They're small, they're checked in-browser, and several — the web crawler at the end in particular — force you to actually reason about concurrent access rather than copy a pattern.

What the tour is not

It's a syntax tour, and it says so in its name. There's nothing on how to structure a Go project, nothing on modules and dependency management beyond the basics, nothing on testing, and nothing on the standard library beyond what the examples need. Error handling gets the mechanics without the idioms, which is a real gap given how much of writing Go is deciding what to do with errors.

The concurrency section is also the thinnest relative to its importance. Goroutines and channels are introduced clearly, but context, cancellation, worker pools, and the ways concurrent Go actually goes wrong in production are all out of scope. Finish the tour and you can write a goroutine; you cannot yet debug one that's leaking.

Who it's for — and who should skip it

The right first hour for any experienced programmer picking up Go. If you already know another statically typed language, this is very likely all the introduction you need before reading real code.

Skip it if programming is new to you — the tour assumes you know what a function and a pointer are and moves briskly. Go by Example or a structured course will be kinder. Skip the generics section on a first pass too, unless you have a reason to need it.

Our take

Close to a perfect language introduction: short, interactive, official, and honest about its scope. The gap is what comes next — the tour ends abruptly with no obvious bridge to writing an actual Go program, and the concurrency material stops right before the part that matters.