https://www.nilpointer.blog/tags/best-practices/Recent content in Best Practices on A Blog for the UninitializedHugoen-us<a href="https://www.apache.org/licenses/LICENSE-2.0" target="_blank" rel="noopener">Licensed under Apache 2.0</a>Wed, 25 Feb 2026 16:40:18 -0800https://www.nilpointer.blog/posts/2026/02/golangs-unbuffered-and-buffered-channels/Wed, 25 Feb 2026 16:40:18 -0800https://www.nilpointer.blog/posts/2026/02/golangs-unbuffered-and-buffered-channels/<p>From the <a href="https://go.dev/blog/codelab-share" target="_blank" rel="noopener noreferrer" >official Go Blog</a>:</p> <blockquote> <p>Do not communicate by sharing memory; instead, share memory by communicating.</p> </blockquote> <p>They&rsquo;re awesome because they enable concurrency support &ldquo;out of the box&rdquo;.</p> <p>They&rsquo;re basically their own type that implements concurrent safe logic of sharing memory locations of data without the explicit usage of mutexes or locks. The example in the blog link above has some code blocks that show this quite well, actually.</p> <p><strong>They can be buffered or unbuffered.</strong></p>