Quoting Daniel Stenberg
- ID
- 47887
- Status
- summarized
- Published
- 18 Nov 2026, 11:58 PM
- Fetched
- 19 Nov 2026, 12:54 AM
- Provider
- Simon Willison
- Category
- developer-ai
- Original URL
- https://simonwillison.net/2026/Nov/18/daniel-stenberg/
- Source URL
- https://simonwillison.net/atom/everything/
Summary
- Score
- 7.5
- Created
- 19 Nov 2026, 12:55 AM
- Tags
- Audience
- developersvibe_codersai_agent_users
What happened
Daniel Stenberg is quoted saying that while agents converted 185,000 lines of C code into 340,000 lines of Rust, the actual curl project merged over 300 commits in a little more than three weeks, including just over 200 bugfixes and a few vulnerability fixes. In another month, curl added another roughly 200 bugfixes and possibly more vulnerability fixes. He asks whether the Rust rewrites/clones will keep up.
Why it matters
If you are evaluating an agent-generated Rust port or clone of a C library, do not treat 185k-to-340k lines of generated code as progress; check whether it has absorbed the upstream project's 300+ commits, 200+ bugfixes, and vulnerability fixes before replacing anything. The quote gives a concrete parity test: compare against actual upstream maintenance, not line count.
Discussion angle
What acceptance criteria would you require before trusting an agent-generated port of a widely used C library—upstream commit parity, CVE backports, fuzzing, or something else—rather than LOC or a passing test suite?