<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software-Engineering on Bytes and Bolts</title><link>https://bytes-and-bolts.info/categories/software-engineering/</link><description>Recent content in Software-Engineering on Bytes and Bolts</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 Matt Delashaw</copyright><lastBuildDate>Sun, 26 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bytes-and-bolts.info/categories/software-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>RTL-SDR Next: Bringing Software Defined Radio into the Modern Async Era with Rust</title><link>https://bytes-and-bolts.info/posts/rtlsdr-next-modern-rust-driver/</link><pubDate>Sun, 26 Apr 2026 00:00:00 +0000</pubDate><guid>https://bytes-and-bolts.info/posts/rtlsdr-next-modern-rust-driver/</guid><description>&lt;p>For over a decade, the &lt;code>librtlsdr&lt;/code> C library has been the bedrock of the SDR community. It is the &amp;ldquo;old gold&amp;rdquo; of the hobby—reliable, ubiquitous, but fundamentally anchored in the coding patterns of 2013. As hardware has evolved, particularly with the release of the &lt;strong>Raspberry Pi 5&lt;/strong> and the &lt;strong>RTL-SDR Blog V4&lt;/strong>, the gap between what the hardware can do and what the legacy drivers provide has widened.&lt;/p>
&lt;p>Enter &lt;strong>rtlsdr-next&lt;/strong>: a high-performance, asynchronous, and safety-first Rust implementation designed to bring the RTL2832U into the modern era.&lt;/p></description></item></channel></rss>