curl Rust rewrite gap
4 Schritte1 Beiträge7 Quellen
The subject is the maintenance gap between AI-generated Rust rewrites of curl and the actively developed C original. In late 2025, a project named urlx appeared as a memory-safe reimplementation. In November 2026, a second project titled "curl, rewritten in Rust" emerged, claiming to have spent $8,600 in compute costs to convert 185,000 lines of C into 340,000 lines of Rust using AI agents over three weeks. Daniel Stenberg, the maintainer of the official curl project, highlighted that during this same three-week period, the actual curl repository merged over 300 commits, including more than 200 bugfixes and several security patches that were absent from the Rust clones. He noted that another 200 fixes landed in the subsequent month. Stenberg argued that while AI can reproduce a static snapshot of well-documented code, it cannot replicate the continuous iteration, community feedback, and stability guarantees built over decades. He provided data showing that only 17.3% (14 out of 81) of curl's confirmed vulnerabilities in 2026 were likely caused by memory safety issues, meaning a Rust rewrite would still have contained 67 of those bugs. The core disagreement lies in whether these rewrites are viable long-term alternatives or merely proof-of-concept demonstrations. Readers should watch for whether the maintainers of the Rust projects implement mechanisms to sync with upstream commits and if they address the remaining non-memory-safety vulnerabilities.
Wie es dazu kam
Late 2025: A project named urlx appears, claiming to be a memory-safe, from-scratch reimplementation of curl and libcurl.
thenextgentechinsider.com ↗November 2026: A second project, "curl, rewritten in Rust," emerges, reporting $8,600 in AI compute costs for converting 185,000 lines of C to 340,000 lines of Rust in three weeks.