<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Rishikesh Sripad Betigeri</title><link>https://rishikesh01.github.io/blog/</link><description>Recent content in Blog on Rishikesh Sripad Betigeri</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0530</lastBuildDate><atom:link href="https://rishikesh01.github.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Go's default concurrency performance is surprisingly hard for Rust to match</title><link>https://rishikesh01.github.io/blog/go-default-concurrency-vs-rust/</link><pubDate>Sat, 19 Sep 2026 00:00:00 +0530</pubDate><guid>https://rishikesh01.github.io/blog/go-default-concurrency-vs-rust/</guid><description>&lt;p&gt;So this week I had a thought about how Rust would perform against Golang in concurrency and CSP.&lt;/p&gt;
&lt;p&gt;For this benchmark, I used Claude Code to write the entire &lt;a href="https://github.com/Rishikesh01/benchmark_rust_and_go_currency"&gt;benchmark suite&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Turns out that default Tokio and its channels lag considerably behind Golang in many cases.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Default Tokio vs Crossbeam vs Go&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Crossbeam is included mainly as a channel baseline. It uses OS threads rather than Tokio&amp;rsquo;s async runtime, so this isn&amp;rsquo;t an apples-to-apples runtime comparison. I wanted to see how much of the difference was coming from the channel implementation itself.&lt;/p&gt;</description></item><item><title>Why my homeserver runs Docker Compose, not Kubernetes</title><link>https://rishikesh01.github.io/blog/why-my-homeserver-runs-docker-compose-not-kubernetes/</link><pubDate>Sun, 09 Aug 2026 00:00:00 +0530</pubDate><guid>https://rishikesh01.github.io/blog/why-my-homeserver-runs-docker-compose-not-kubernetes/</guid><description>&lt;p&gt;I had Kubernetes installed on my homeserver. I still chose Docker Compose.&lt;/p&gt;
&lt;p&gt;Not because Kubernetes couldn&amp;rsquo;t run it. It absolutely could. I chose Compose
because the entire point of this server was to make my life easier, and I know
exactly where &amp;ldquo;I should probably just use Kubernetes&amp;rdquo; ends for me.&lt;/p&gt;
&lt;p&gt;Let me back up.&lt;/p&gt;
&lt;p&gt;I always wanted to have a server of my own. The list of what I needed was pretty
basic:&lt;/p&gt;</description></item></channel></rss>