Actual Curl Rewrites in Rust
sohkamyung
13 points
3 comments
November 17, 2026
Related Discussions
Found 5 related stories in 150.6ms across 13,334 title embeddings via pgvector HNSW
- How is the Bun rewrite in Rust going? tomlockwood · 463 pts · July 27, 2026 · 62% similar
- 1,500 Curl Authors speckx · 15 pts · July 25, 2026 · 59% similar
- Cloudflare is rewriting everything in Rust tonyedgecombe · 24 pts · October 22, 2026 · 59% similar
- How Our Rust-to-Zig Rewrite Is Going jorangreef · 467 pts · July 16, 2026 · 58% similar
- Bun 1.4 Rust rewrite is not looking good? tipiirai · 136 pts · August 19, 2026 · 57% similar
Discussion Highlights (2 comments)
goodmythical
Wow, I'm kind of ashamed how eye-opening this article is. curl is definitely one of those 99% invisible "so perfect I never notice it" things. I mean, I use it. I see it pop up in dnf update, but I had no idea of the update cadence. 1,306 contributors, 99 versions, ~17k closed PRs, ~5,700 closed issues Anyway, interesting to see "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."
fschuett
It's not just about vulns, it's that Rust has a "compile anywhere" (even WASM) that C just doesn't have. I can pull a few Rust libraries that do different things together and make something new from it, with C, good luck with all the Makefiles. And the small improvements that accumulated can be ported too, when doing Rust rewrites, I would not say that this is an argument for sticking with C per se. And 20% less vulns is still 20% less.