Improving JavaScript Bundler Performance with Rust-Based Glob Pattern Matching t

<h2> A 14-Second Build Dropped to 3 Seconds, Then Everything Else Went Wrong </h2> <p>Six months ago, our API was a standard Express + TypeScript setup running on Node.js 22. It

<p>Let’s be honest. When we talk about migrating a service to Rust, we all envision the same thing: liquid-lightning latency, CPU graphs dropping off a cliff, and a single server

<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>TL;DR: I ported Python's natsort library to Rust for Port Mortem 2026.</p> <p>Writing the sorting algorithm turned out to be the easy part.</p> <p>The difficult part was

<h1> I Ported mustache.js to Safe Rust in 72 Hours — Here's What Actually Broke </h1> <p>By <strong>Gargee Bhattacharjee</strong> | <strong>Port Mortem 2026</strong> |

<h1> The Case for Rust: Why I Choose Absolute Reliability for RPGFX and WebRaven </h1> <p>The transition from high-level, interpreted languages to Rust often feels less like a

<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>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