Go's Concurrency Is About Structure, Not Speed: chan and context as Lifecycle Primitives

For a while, I thought channels were Go's way of doing message passing. Something like Erlang processes or actors, except with a simpler syntax. That understanding is fine if you're writing tutorials. It is not fine when you've just OOM-killed a pod ...