<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Async on Mi&amp;Bee Blog</title><link>https://blog.mickeyzzc.tech/en/tags/async/</link><description>Recent content in Async on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Sat, 30 May 2026 15:00:00 +0800</lastBuildDate><atom:link href="https://blog.mickeyzzc.tech/en/tags/async/rss.xml" rel="self" type="application/rss+xml"/><item><title>Standard Library, Concurrency, and async: Rust Chapter Finale</title><link>https://blog.mickeyzzc.tech/en/posts/programming/rust-stdlib-concurrency-async/</link><pubDate>Sat, 30 May 2026 15:00:00 +0800</pubDate><guid>https://blog.mickeyzzc.tech/en/posts/programming/rust-stdlib-concurrency-async/</guid><description>&lt;p&gt;After the journey of the first four articles—ownership and borrowing, type system, error handling, and pattern matching—we have now reached the Rust chapter finale, time to tie the scattered knowledge together.&lt;/p&gt;
&lt;p&gt;This article focuses on Rust&amp;rsquo;s standard library concurrency tools and the async/await ecosystem. These are the most interesting comparative points between Rust and Go in the concurrency domain: Go makes concurrency look simple through goroutines and channels, while Rust makes concurrency safe and reliable through strict type systems and ownership constraints.&lt;/p&gt;</description></item></channel></rss>