curl
4 节点1 篇7 来源
本主题聚焦于AI生成的Rust版curl重写项目与持续维护的C语言原版之间的维护差距。2025年末,名为urlx的项目作为内存安全的重新实现出现。2026年11月,第二个名为“curl, rewritten in Rust”的项目涌现,声称使用AI代理在约三周内花费8,600美元计算成本,将18.5万行C代码转换为34万行Rust代码。curl官方维护者Daniel Stenberg指出,在这相同的三周期间,实际curl仓库合并了超过300个提交,其中包括200多个bugfix和若干安全补丁,而这些修复在Rust克隆版本中完全缺失。Stenberg强调,虽然AI可以复现文档完善的静态代码快照,但无法复制数十年来通过社区反馈和持续迭代建立的稳定性保证。他提供数据显示,2026年已确认的81个curl漏洞中,仅17.3%(14个)可能由内存安全问题引起,这意味着Rust重写版本仍会包含其余67个漏洞。核心争议在于这些重写项目是可行的长期替代品还是仅为概念验证。读者应关注Rust项目维护者是否建立同步上游提交的机制,以及他们如何处理非内存安全类的剩余漏洞。
事情怎么走到这一步
A project named urlx appears, claiming to be a memory-safe, from-scratch reimplementation of curl and libcurl. (Approximate date based on 'late 2025' description in source).
thenextgentechinsider.com ↗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. (Approximate date based on 'November 2026' description).
thenextgentechinsider.com ↗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 ↗Simon Willison quotes Stenberg's findings on his weblog, amplifying the discussion on AI coding limitations.