<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Context on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/context/</link><description>Recent content in Context on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Thu, 12 Mar 2026 14:00:00 +0800</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/context/rss.xml" rel="self" type="application/rss+xml"/><item><title>Concurrency: The Art of Goroutines, Channels, and Context</title><link>https://blog.mickeyzzc.tech/en/posts/programming/go-concurrency/</link><pubDate>Thu, 12 Mar 2026 14:00:00 +0800</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/programming/go-concurrency/</guid><description>&lt;p&gt;Concurrency is the core feature that distinguishes Go from other languages. Unlike C++/Java&amp;rsquo;s thread model, and unlike JavaScript&amp;rsquo;s single-threaded event loop, Go provides a set of concurrency primitives — goroutines, channels, and context — that let you write high-performance concurrent programs with relatively straightforward code.&lt;/p&gt;
&lt;p&gt;This article covers the technical details of Go&amp;rsquo;s concurrency model: the underlying scheduling mechanism, the implementation of channels and context, common concurrency patterns, and performance optimization and best practices.&lt;/p&gt;</description></item></channel></rss>