AI NewsProductivityReported

Curl author on AI rewrites: 185,000 lines converted, 300 commits meanwhile

Daniel Stenberg, curl's maintainer, says two AI-driven Rust rewrites ran while his team merged 300 commits on the real project.

AI News

Editorial2 min read

LinkedInX
Reveneau illustration of an AI agent rewriting C code into Rust while a maintainer merges bugfixes

Why it mattersA full AI rewrite is cheap to start and expensive to keep running. The living project it tries to replace is already moving.

An AI agent can convert 185,000 lines of C to Rust for about $8,600. The project it is replacing keeps moving every day. Daniel Stenberg, the author and maintainer of curl, wrote about two AI-driven Rust rewrites of curl on his blog. He makes one point first. The rewrites are not the same project as his.

Stenberg names two attempts. The first, called urlx, is a memory-safe from-scratch reimplementation of curl and libcurl. It has existed for several months. The second is a new Rust rewrite, also confusingly called curl. Its authors say the conversion spent about $8,600 in AI API costs. Stenberg writes that he has not been in contact with the people behind either rewrite. Every figure in the post is Stenberg's own or quoted from the rewrites' authors.

The number the rewrite authors give

Stenberg writes that the agents turned 185,000 lines of C into 340,000 lines of Rust. He adds a frame. In the same window, the real curl project merged over 300 commits. Those commits included roughly 200 bugfixes. A few of them patched real vulnerabilities. The moving project keeps moving.

The gap matters, because a Rust fork that catches up to the original is a fork that keeps paying. Each one of those 300 commits would have to be re-done in Rust. Then the next 300 would need the same work again.

The case for Rust is smaller than it looks

Stenberg counts the 81 vulnerabilities confirmed in curl in 2026. He writes that 14 of them would most likely have been avoided in a memory-safe language like Rust. That is 17 percent. The other 67 would be in the Rust version as well. Memory safety, in his data, prevents about one in six curl bugs. A full rewrite does not touch the other five in six.

What Stenberg thinks the real project does

Stenberg writes that the constant tweaking, fixing, improving and extending is what makes a software project live. He credits a working community of users, contributors and maintainers. A codebase is cheap to make. A maintainer group is years of work. The Rust rewrites do not appear to have one yet. Their repositories hold code with no community around it.

Any engineering leader looking at an AI-driven migration should read this post before approving the budget. The upfront cost is tiny. The ongoing maintenance cost is the real one. Nobody has paid that cost yet on a rewritten project at this scale. A one-off conversion is a prototype. Stenberg's question is whether the prototype gets a community before the existing project lands another thousand commits.

Source

Actual curl rewrites in rust on daniel.haxx.se.

Reported bydaniel.haxx.se

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

Share
LinkedInX
Start a project