Curl maintainer rejects AI Rust rewrites
curl maintainer Daniel Stenberg addressed recent attempts by AI agent clusters to rewrite curl in Rust, emphasizing that automated code translation cannot replace continuous maintenance and edge-case hardening. While AI agents converted 185k lines of C into 340k lines of Rust, upstream curl merged over 200 bug fixes and multiple security patches during the same three-week span.
AI coding agents make wholesale codebase translations cheap to generate, but they mistake a static snapshot for a living project. Translating code once is a party trick; the true value in core infrastructure lies in ongoing triage, active hardening, and an experienced maintainer community.
- –Maintenance velocity outpaces translation: During the three weeks agents spent using $8,600 in compute to rewrite curl, upstream merged 300+ commits and resolved 200 bugs that the Rust forks immediately lacked.
- –Language safety does not equal total security: Stenberg points out that only 17.3% of curl's 2026 vulnerabilities stemmed from memory-safety issues, meaning over 80% of logic and protocol flaws would persist in Rust.
- –Agent translation bloat: The automated rewrite expanded curl's 185,000 lines of C into 340,000 lines of Rust, illustrating how agentic porting frequently trades idiomatic design for repetitive generated boilerplate.
- –Test harness dependency: These rewrites only succeeded because curl provided nearly three decades of exhaustive documentation, API contracts, and thousands of verification tests for the models to lean on.
DISCOVERED
3h ago
2026-11-19
PUBLISHED
3h ago
2026-11-19
RELEVANCE
AUTHOR
The PrimeTime