Bun has been converted to rust. Now what?
bytecode.news
June 3, 2026
8 min read
🔥🔥🔥🔥🔥
43/100
Summary
Bun has transitioned to Rust with over a million lines of code and 6,755 commits, primarily generated by Claude Code agents in nine days. The previous Zig implementation has been removed following Anthropic's acquisition of Bun in December.
Key Takeaways
- Bun's codebase was rewritten in Rust, merging over a million lines of code generated by Claude Code agents, with 6,755 commits completed in nine days.
- The Rust implementation passed 99.8% of the existing test suite but contains over 10,000 unsafe blocks, indicating a lack of memory safety despite the stated motivation for the rewrite.
- The primary reason for the conversion to Rust was to address memory safety issues that plagued the previous Zig implementation, but the faithful porting strategy did not achieve the desired safety improvements.
- The benchmarks for the new Rust implementation are neutral-to-faster, and the binary size decreased by a few megabytes compared to the original Zig version.
Community Sentiment
Positives
- The Rust rewrite of Bun passing 99.8% of the existing test suite indicates a high level of reliability and correctness, which is crucial for maintaining trust in the new implementation.
- The transition to Rust could enhance performance and safety, given Rust's strong emphasis on memory safety and concurrency, potentially leading to more robust applications.
Concerns
- Concerns about the accuracy of the 99.8% test suite coverage raise questions about the thoroughness of the rewrite process, suggesting that the transition may not be as seamless as claimed.
- The significant density of 'unsafe' code in Bun compared to similar projects indicates potential risks and challenges in maintaining safety and stability, which could impact user trust.
