<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>rust on #anooptube</title>
    <link>https://anooptube.in/tags/rust/</link>
    <description>Recent content in rust on #anooptube</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 15 Aug 2026 19:48:00 +0530</lastBuildDate><atom:link href="https://anooptube.in/tags/rust/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>C&#43;&#43; vs Rust vs Go in 2026: Which One Should You Actually Learn?</title>
      <link>https://anooptube.in/blog/post49/</link>
      <pubDate>Sat, 15 Aug 2026 19:48:00 +0530</pubDate>
      
      <guid>https://anooptube.in/blog/post49/</guid>
      <description>Every few months someone asks me the same question: &amp;ldquo;should I learn Rust or just stick with C++?&amp;rdquo; Lately Go gets thrown into that question too. I&amp;rsquo;ve written a lot of C++, poked at Rust, and shipped small things in Go — so here&amp;rsquo;s my honest 2026 take, backed by what&amp;rsquo;s actually happening in the ecosystem right now, not vibes.
Why this comparison actually matters in 2026 This isn&amp;rsquo;t an academic exercise.</description>
    </item>
    
  </channel>
</rss>
