독서리서치레이더투자 프레임워크
로그인 / 회원가입
← 읽기로 돌아가기
뉴스주제 · curl Rust rewrite gap간단한 요점2 분 소요DisconfirmAI 편집부

curl Maintainer Daniel Stenberg: AI Rewrote 340,000 Lines of Rust but Missed 200 Concurrent Bugfixes

curl project maintainer Daniel Stenberg released a direct comparison showing that while an AI agent spent over three weeks converting 185,000 lines of C code into 340,000 lines of Rust code, the actual curl project merged over 300 commits in that same period. These included more than 200 bugfixes and several security patches that the Rust rewrite completely lacked. His question is: Can these clones keep up?

2026-11-18 23:58 GMT+8

Code volume has never been a measure of maintenance quality. In a blog post dated November 17, 2026, curl maintainer Daniel Stenberg provided a starkly specific comparison: an AI agent converted 185,000 lines of C code into 340,000 lines of Rust, nearly doubling the line count. Yet, during that same timeframe, the actual curl project merged over 300 commits. Among them were more than 200 bugfixes and several security vulnerability patches—none of which are present in those Rust rewrites.

Stenberg specifically noted, "I counted." This was not a vague impression but a line-by-line verification by the maintainer across two timelines. Over those slightly more than three weeks, human maintainers fixed over 200 bugs and patched several vulnerabilities; the AI produced new code nearly twice the size of the original yet remained entirely disconnected from these fixes. He further noted that in the following month, the team performed another 200 fixes, possibly patching additional vulnerabilities.

These figures reveal a structural blind spot: AI agents excel at one-time conversions—moving existing code from one language to another—but struggle to continuously track incremental changes in upstream projects. An actively maintained open-source project generates bugfixes, security patches, and compatibility fixes daily; these changes do not appear in the initial code snapshot. The rewriting agent sees only the starting point, whereas maintainers perform continuous convergence. Those 340,000 lines of Rust code may be syntactically correct and structurally clear, but they do not contain the specific errors fixed by those 200 bugfixes, nor the attack surfaces closed by those vulnerability patches.

로그인 / 회원가입
독서리서치레이더투자 프레임워크

The question Stenberg left behind is rhetorical: "Will these clones keep up?" He offered no answer and did not assert that AI rewrites can never catch up. His phrasing was an open-ended query rather than a definitive negation. However, the data itself is telling: at the moment the code conversion was completed, those Rust versions were already lagging behind the upstream. Catching up requires continuous synchronization capability, not merely the scale of an initial conversion.

Notable boundary conditions: Stenberg described a specific batch of AI agents attempting to rewrite curl, not a final judgment on all AI-assisted programming. Curl itself is a project with over 25 years of maintenance history, continuously handling protocol compatibility and security issues; its maintenance complexity may exceed that of many one-time conversion scenarios. His observation applies more to the question of whether "actively maintained large projects can be replaced by one-time rewrites" rather than "whether AI can write useful code."

출처

  • simonwillison.netSimon Willison’s Weblog↗
주제

curl Rust rewrite gap

The subject is the maintenance gap between AI-generated Rust rewrites of curl and the actively developed C original. In …

4 단계1 건업데이트됨 2026-11-21 15:44

현재까지의 과정

  1. 2025-12-01Late 2025: A project named urlx appears, claiming to be a memory-safe, from-scratch reimplementation of curl and libcurl.thenextgentechinsider.com ↗
  2. 2026-11-01November 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.thenextgentechinsider.com ↗
  3. 2026-11-17November 17, 2026: Daniel Stenberg publishes a blog post comparing the rewrites to upstream activity, noting 300+ commits and 200+ bugfixes missed by the clones during the conversion period.daniel.haxx.se ↗

아직 해결되지 않은 문제

  • Will the maintainers of the Rust rewrites establish automated pipelines to track and merge upstream curl bugfixes?
  • Do the Rust implementations address the 67 non-memory-safety vulnerabilities identified by Stenberg?
  • Are these projects intended as production-ready alternatives or strictly as proofs of concept for AI code translation?
전체 주제 읽기 →
리서치 계속하기 →