*The Rustification of Bun#
Rewriting 500,000 lines of Zig into another language would be a gargantuan undertaking if done by hand. “A rewrite in another language would take a small team of engineers a full year. It would mean freezing bugfixes, security fixes or feature development for that time,” Sumner wrote.
Instead, Sumner went with Claude. He spun up about 50 dynamic Claude Code workflows, reaching a peak of about 1,300 lines of code per minute and generating over a million lines of Rust code. The job took 11 days and cost about $165,000 at API pricing. Claude Fable did most of the heavy lifting.
To a degree, sure, but going out of your way to go against convention even for the language itself is also to blame if Kelly is right. It’s less about whether you add type annotations to python, and more about following conventions and writing python in a way that a random developer with enough python experience would be able to understand and contribute to the codebase. I’ve seen anti patterns in a handful of languages I know well enough and it’s easy to tell the other person didn’t bother practicing enough and learning basic conventions.
Coding conventions are fine but generally the language should enforce them by design. This is the difference between Rust and Zig. In Zig, you can ignore memory safety. In Rust you can’t (or rather, it’s hard to). Type systems are the same, you generally can’t just ignore the rules. The compiler will complain.