Back to Devoured - November 18, 2026
DEVOURED
Actual curl rewrites in rust

Actual curl rewrites in rust

Tech Daniel.haxx.se
Daniel Stenberg explains why AI-generated Rust rewrites of curl fail to capture the project's true value: ongoing community maintenance and vulnerability remediation.
What: Daniel Stenberg notes that several projects have used AI to rewrite curl's 185,000 lines of C code into roughly 340,000 lines of Rust. Stenberg points out that during the three weeks these rewrites took, the actual curl project merged over 300 commits and 200 bugfixes, proving that language safety is only a small part of the maintenance challenge.
Why it matters: This illustrates the common misconception that software is primarily about the source code, rather than the ongoing, iterative community process of security patching and API stability required for long-lived infrastructure.
Deep dive
  • curl's longevity is driven by decades of feedback, bug tracking, and API/ABI stability, not just the underlying language.
  • AI rewrites converted 185k lines of C to 340k lines of Rust in weeks.
  • Stenberg notes that while 17.3% of 2026 curl vulnerabilities were memory-related and preventable by Rust, 82.7% would have persisted in a Rust rewrite.
  • The core difficulty of building a curl alternative is keeping pace with the project's ~11 commits per day, not the initial implementation.
  • Stenberg argues that constant refactoring and community engagement are more effective than monolithic rewrites.
Decoder
  • ABI (Application Binary Interface): The interface between two binary program modules, often defining how functions are called and how data is structured at the machine code level, crucial for library compatibility.
  • Memory-safe: A property of programming languages that prevents common bugs like buffer overflows, dangling pointers, or memory leaks that frequently lead to security vulnerabilities in C.
Original article

For a long time we have received repeated requests for, or questions about, a curl rewrite in rust. Often as a joke, but also seriously.

In this modern world of AIs, we have only been waiting for someone to prove it possible and now it seems we don’t have to wait anymore.

This fall seems to be the time of the curl-in-rust takes as we first saw urlx appear a few months ago, claimed to be a memory-safe, from-scratch reimplementation of curl and libcurl and now in November curl, rewritten in Rust – a rewrite of curl and libcurl in Rust. This second one confusingly enough not even using a different name.

This latter one claims to have spent 8,600 USD to make it happen.

Writing code once was never the issue

Writing code once was never the big deal with software and it still isn’t. Sure, it’s fascinating that you can make a set of agents accomplish this in only a few weeks but let’s face it: it could do this because all the AIs of the world have trained on curl code for years. curl is extremely well documented, there are hundreds of existing open source application using its API and there are thousands of test cases to verify the implementation.

The C code sits there and all the AI needs to do is convert it to rust, then polish until the tests work.

curl is the result of time

curl has come to be what it is thanks to many decisions, lots of time, many users, oceans of feedback and many iterations. Sure, recreating what curl is at any specific single moment in time is certainly doable. Doable, because we have made a perfect specification for that project.

Behind already

During the time these agents converted 185,000 lines of C code into 340,000 lines of Rust code (I counted), we merged over 300 commits in the actual curl project. We actually improved curl during these a little more than three weeks. A little over 200 bugfixes actually. 200 bugfixes that none of those rust rewrites have. We also fixed a few vulnerabilities. In another month we have done another 200 and maybe fixed a few more vulnerabilities. Will these clones keep up?

The constant tweaking, fixing, improving and extending is what makes a software project live, what makes it attractive to users and what makes it able to compete with alternatives.

That fixing, and occasional new feature, is a direct result of a working community of users, contributors and maintainers. That goes way beyond the source code or which language that is used.

A primary reason it is hard to make a competing curl alternative is because of the development speed, the development team and the community around curl. It is not because of the chosen language it is implemented in. Only curl can boast decades of ABI and API stability and prove that we know this and can do it well – over time. An alternative that pops up today might be able to do it as well, and in a few decades we will know if they could.

C

I know I’m repeating myself but: out of the 81 vulnerabilities we have confirmed in curl so far during 2026, 14 were the result of mistakes that most likely would have been avoided had we used a memory-safe language such as rust. That’s 17.3%.

A Rust implementation of curl would thus still have had 67 of those vulnerabilities.

No rewrites

I don’t believe in rewrites into any language. I believe in constant and never-ending polishing, iterating and refactoring.

Those rewrites

I should add that I have not been in contact with any of the people behind these rewrites, and if there are two I bet there are more that I just haven’t seen yet. I only know of them because people have pasted me links to their repositories.

I don’t know what they will do with those projects going forward. Are they anything more than proof of concepts? I presume we will find out.

They can of course follow along our commits and convert them to rust on the fly if they want – we only do about 11 commits per day on average. Or maybe they ignore the bugreports or maybe they take their projects in other directions?

I wish them good luck whatever they decide!

How do I feel about them?

Several people asked me this.

Imitation is the sincerest form of flattery that mediocrity can pay to greatness. / Someone

I’m amused. A little puzzled. Fascinated. They spent their money and effort on that?

Explore all 55 articles in today's digest

Fresh dev news, AI-digested daily. Never miss a trend at devoured.fyi