What if “modernizing” legacy software didn't mean rewriting it and hoping nothing breaks? What if we...
What if “modernizing” legacy software didn't mean rewriting it and hoping nothing breaks?
What if we could take a small, battle-tested C library, rebuild it in a modern language, and prove that the new implementation still behaves like the original?
That was the challenge I took on during Code Resurrection 2026.
Our project: TinyExpr → tinyexpr-rs, a safe, idiomatic Rust port of the original TinyExpr mathematical expression parser and evaluator.
And the surprising part?
There's a joke that every Rust project starts with someone saying "we should rewrite this in Rust"...
Port Mortem 2026 — Rewrite Real Software. Prove It Still Works. The software industry is...
Exploring the convergence of memory-safe systems programming, retrocomputing mental models, and language server protocols to…
This is a submission for DEV's Summer Bug Smash: Clear the Lineup. Project Overview Typst...
A step-by-step story about reusable async functions, boxed futures, restartable tasks, and the tiny Tokio task manager I built…
How I built a two-tier closure JIT compiler in Rust and solved the lifetime reference problem using Higher-Ranked Trait Bounds…
