
I used AI to rewrite my entire Go engine in Rust in 2 days. 60+ files, zero shortcuts.
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 away and rewrite it in Rust. I did it in 2 days, with AI doing most of the heavy lifting. This is the honest account of how that went: what worked, what didn't, and whether the result was actually worth it. The setup smplogs is a tool that analyzes AWS CloudWatch log exports entirely in your browser. The analysis engine is compiled to WASM and runs client-side. Logs never touch my server. The Go engine had been running in production for months. It handled Lambda, API Gateway, and ECS parsing. It had anomaly detection, log clustering, T-Digest streaming percentiles, cold start detection, and a full parity test suite. It wasn't small. 55 Go source files. 17,000+ lines. All of it needed to produce byte-for-byte identical output to pass the parity tests. Why bother? Honest reasons, not post-hoc rationalization: Speed.
Continue reading on Dev.to
Opens in a new tab



