Porting natsort to Rust taught me that "it compiles" is the easy 5%

<p>Every "port to Rust" post is the same shape: <em>I rewrote it in Rust and it's faster.</em> This one isn't. I ported a Python string-similarity library to Rust, and the honest

<p>I built a multi-tenant DNS/email security audit app — <a href="https://github.com/mgoolden17-cyber/dnslint" rel="noopener noreferrer">dnslint</a> — as a portfolio piece over a

<p><em>A Port Mortem 2026 write-up about a JavaScript to Rust port, one strange Unicode character, and what green tests do not tell you.</em></p> <p>The first benchmark result was

<p>There's a joke that every Rust project starts with someone saying "we should rewrite this in Rust" and ends four weekends later with a half-finished repo and a lot of new

<p>A few weeks ago I had a working analysis engine written in Go, compiled to WASM. It worked. It was 60+ files, thousands of lines, battle-tested. And I decided to throw it all

<p>After benchmarking all four languages across 23 production workloads, the data reveals which will dominate the next decade of systems… </p> <h3> The Future of Systems

<p>I needed a fast OpenAI client for a realtime voice agent project. The official Python SDK is great, but I needed Rust — for WebSocket audio streaming, edge deployment to

<p>Build production-grade kernel modules in 60 seconds — with tests, GitHub Actions, and compile-time safety that caught 23 crashes before… </p> <h3> Rust Kernel Modules,