https://brtkwr.com/tags/concurrency/Recent content in Concurrency on brtkwr.comHugoenMon, 20 Apr 2026 01:00:00 +0000https://brtkwr.com/posts/2026-04-20-what-makes-go-channels-special/Mon, 20 Apr 2026 01:00:00 +0000https://brtkwr.com/posts/2026-04-20-what-makes-go-channels-special/<h2 id="tldr"> TL;DR <a class="heading-link" href="#tldr"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h2> <p>A Go channel is one primitive covering what other languages split across locks, condition variables, semaphores, and queues. That consolidation is the thread I kept pulling on while reading.</p> <h2 id="motivation"> Motivation <a class="heading-link" href="#motivation"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h2> <p>Channels come up in every Go pitch. I wanted to understand why.</p> <h2 id="what-a-channel-actually-is"> What a channel actually is <a class="heading-link" href="#what-a-channel-actually-is"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h2> <p>In most languages you get shared memory plus coordination tools: mutexes for exclusion, condition variables for waiting, semaphores for counting, queues for handoff. Synchronisation and data are separate problems with separate primitives.</p>