← Go, End to End

Go, End to End

The Standard Library Philosophy

Go ships an unusually complete standard library for a language its age. HTTP clients and servers, JSON, XML, cryptography, compression, templating, testing, all in the box, no third-party package required to get something real running. That's a deliberate design choice, not an accident, and it changes how you evaluate whether you need a dependency at all.

Why this matters practically

In a lot of ecosystems, "I need to make an HTTP request" or "I need to hash a password" means picking a third-party library first, evaluating its maintenance status, and adding it to your dependency tree. In Go, the honest first move is checking whether net/http, crypto/bcrypt, or similar already does it, because it usually does, and it's maintained by the Go team with the same backward-compatibility guarantees as the language itself.

A practical tour (not exhaustive)

  • net/http, HTTP client and server, no framework needed for a basic server (see the next chapter)
  • encoding/json, encoding/xml, encoding/csv, structured data formats
  • context, cancellation and deadline propagation (its own dedicated coverage in the concurrency chapters)
  • crypto/* (sha256, bcrypt via golang.org/x/crypto, tls), cryptography and secure connections
  • time, dates, durations, timers, tickers
  • regexp, regular expressions
  • os, io, bufio, files and streams (previous chapter)
  • sync, sync/atomic, concurrency primitives (previous chapters)
  • testing, tests and benchmarks, no external framework (previous chapter)

Notice golang.org/x/crypto in that list: the golang.org/x/* repositories are maintained by the Go team but ship outside the main standard library (usually because they need to evolve faster than the stdlib's stability guarantees allow, or because they're genuinely optional extensions). They're not third-party in the "random package on the internet" sense, more like an extended standard library with slightly looser guarantees.

The practical habit worth building: before reaching for a dependency, spend two minutes checking the standard library and the golang.org/x/* extensions. Often the thing you need is already there, already tested, and already going to be maintained for as long as Go itself is.