<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tokio on N Acharya</title><link>https://nacharya.github.io/tags/tokio/</link><description>Recent content in Tokio on N Acharya</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 N Acharya</copyright><lastBuildDate>Sun, 05 Apr 2026 10:00:00 -0700</lastBuildDate><atom:link href="https://nacharya.github.io/tags/tokio/index.xml" rel="self" type="application/rss+xml"/><item><title>Async Rust with Tokio: Futures, Streams, and Channels — and How They Compare to Go</title><link>https://nacharya.github.io/posts/rust-async-tokio/</link><pubDate>Sun, 05 Apr 2026 10:00:00 -0700</pubDate><guid>https://nacharya.github.io/posts/rust-async-tokio/</guid><description>&lt;p&gt;Go&amp;rsquo;s concurrency model is famously approachable: goroutines are lightweight, channels are built into the language, and &lt;code&gt;context&lt;/code&gt; handles cancellation without much ceremony. But Rust&amp;rsquo;s async story — built on stackless futures, the Tokio runtime, and a rich channel ecosystem — is compelling in a different way. It pushes more decisions to compile time, eliminates data races by construction, and delivers higher concurrency density with less memory.&lt;/p&gt;
&lt;p&gt;This post works through Rust async from first principles and puts it side-by-side with Go at every step.&lt;/p&gt;</description></item></channel></rss>