About
Updated:
Gopheria publishes long-form writing about Go: the language, its runtime, its frameworks, and the ecosystem that has grown around them. The tagline is the editorial policy — Go, beneath the surface. Most of what is written about Go on the open web restates the documentation. This site is interested in the layer underneath it.
Who writes here
Nolan Keir writes about Go, backend engineering, and the systems behind production software. His work focuses on concurrency, runtime behavior, performance, tooling, and the trade-offs hidden behind clean abstractions. He prefers reproducible experiments and measurable behavior over rules of thumb. He writes at Gopheria.
The standard
Every claim on this site about how something behaves or how fast it runs arrives with the means to check it:
- the exact Go version, because runtime behaviour is not eternal;
- the machine it was measured on;
- a command you can run;
- the actual output, pasted rather than summarised.
Benchmarks are run with -benchmem, at least ten times, and compared with
benchstat. Differences are reported with their variance. When a result lands
inside the noise, the article says so and keeps the section — a negative result
is still a result, and it is the kind nobody else publishes.
Where an experiment does not model something, the article states what it misses. One honest sentence about a limitation is worth more than a paragraph of hedging.
Who it is for
Working Go developers who can already read Go fluently and want to know what is happening beneath it: why the scheduler made that choice, what the benchmark is actually measuring, where the abstraction leaks. This is not a place to learn syntax.
How the site is built
A static Astro site, no server, no database, no build-time API keys. Every post
is also served as plain Markdown at its URL plus .md, and the whole corpus is
available at /llms-full.txt — the writing here is meant to be
quotable, by people and by machines.
The site sets no cookies, runs no advertising, has no comment system and collects nothing from you. Analytics, where present, are cookieless and aggregate. See the Cookie Policy for the details and the Privacy Policy for what little is processed.
Contact
Corrections are welcome and get published. If a benchmark here does not reproduce on your machine, that is worth an email — it usually means the article failed to state a condition it depended on.