Code Resurrection 2026 — Port Mortem ran July 31 to August 3, 2026, a 72-hour online sprint with one rule: pick a real, battle-tested repository, rebuild it in a language it was never written in, and prove the rewrite still behaves. 148 teams took on C, TypeScript, Python, JavaScript and Go libraries and turned them into verified ports in Rust, Go and C++. The bar was honest evidence over confident claims, and the top of the field cleared it convincingly, with the leading submissions scoring above 4.2/5.00.
Submissions were assessed by a panel of engineers from Nvidia, Amazon, Google, IBM and leading AI companies, scored on the published criteria: Functionality & Reliability (40%), Behavioral Equivalence (30%), Code Quality (20%), and Innovation (10%). Featured judges:
The Odyssey of FaFa, Porting natsort to Rust taught me that "it compiles" is the easy 5%, The test suite never knew it was running on Rust, Port Mortem Track C: We rewrote isaacs/minimatch (TypeScript) in Go in 48h, I now know more about JavaScript’s regex behavior than I know about my life after graduation. Anyway, I ported Picomatch to Rust., I ported a JavaScript colour library to Rust and made the original test suite run against it, unmodified, Porting decimal.js to Go for Hackathon Raptors, How We Ported Python’s natsort to Rust — And the 133,000 Fuzz Inputs That Proved Us Wrong, I Ported a JavaScript Markdown Parser to Rust in 72 Hours — Here's What Actually Broke, Porting TinyColor to Go took about 11 hours. Proving that it behaved exactly like the JavaScript implementation took several times longer., I ported decimal.js to Go and ran its own 22,658 tests against the result. Four bugs were mine. One was theirs., Port Mortem 2026: Engineering a Behaviorally Equivalent Rust Port of python-semanticversion, I Ported python-semanticversion to Rust in 72 Hours: What Broke, How I Proved Parity, and the 6-Hour Edge Case, Porting C Code to Safe Rust: 22% Performance Gain, From Python to Rust: Rewriting a Real Open Source Project for Port Mortem 2026, I ported croniter to Rust and got 228/228. That number proved nothing, Porting MPack C Library to Pure Python for Hackathon, 41,088 divergences, and four tests that tested nothing, A few days ago, my team and I wrapped up our first porting hackathon and it changed our perspective on AI-assisted coding, My port passes 710 out of 710. Here is everything that number does not tell you., I ported Picomatch to Rust. It passed 1,977 tests and lost the benchmark by 18x, I Ported an 830-Star Python Library to Rust and the Fuzzer Found 12 Bugs — All of Them Mine 🦀, We Rewrote a Cron Library in Rust and then Missed the Deadline Doing It, Porting decimal.js to Go: What Broke and How We Found It, We ported the JS library bytes.js to native Go (GoBytes), 139,907 Calls Later: What It Actually Takes to Port a Numerical Library from JavaScript to Rust, C to Rust Port, The bug that differential fuzzing cannot find, 140 Bugs Were Hiding in One Function, and My Tests Couldn't See Any of Them, Porting qs to Go: an honest account, My port of Python SemVer to Golang for my First Hackathon, I Ported a JS Library to Go — Then Spent Twice as Long Proving It Actually Worked, Porting a Python PEG parser to Rust in 72 hours, and actually proving it worked, We ported JSBI to C++ — and the benchmark taught us more than the port did, I Ported cJSON to Rust, and My Own Test Suite Lied to My Face, robfig-cron-rs: robfig/cron, ported to Rust, I Ported decimal.js to Go in 72 Hours — and Found 2 Real Bugs in the Original, I ported fastest-levenshtein, the fastest string-matching library in the JavaScript ecosystem, to Go, Porting price-parser from Python to Rust: the hard part was proving it still lied the same way, I thought porting TinyExpr to Rust would be easy. Then the tests started disagreeing., Rust Port of Python's natsort with 8 Bugs and 6 Hours on Regex, The Emoji That Broke My Levenshtein Port: A Port Mortem Story, Porting robfig/cron to Rust: How 18,000 Differential Tests & A 6-Hour Timezone Bug Proved "It Compiles" Is Only 5%, Port Mortem 2026 · ported pylev Python Rust · 250k diff tests, 0 mismatches · the Unicode indexing trap is real, Resurrecting TextDistance in Rust for AI Systems, From Python to Rust: We thought we were porting algorithms. We were actually porting behavior.
