Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-27 · high
The project's open pull requests grew from 1,277 to 2,475 since the July 8 rewrite announcement, per Tom Lockwood's July 27 audit.
Why now: Lockwood published the audit on July 27, six weeks after Bun announced the rewrite on July 8.
An independent audit puts Bun's Rust rewrite at roughly $800,000, nearly five times the original $165,000 estimate, per Tom Lockwood's July 27 review.
For Bun users, that gap means still no release tag six weeks after the July 8 announcement. The project hadn't shipped an actual release in 11 weeks. For anyone pricing an AI-driven rewrite of their own, it's the first outside look at what happens once the merge queue starts filling up.
Bun announced the rewrite on July 8. It framed the job as an 11-day sprint, running about $15,000 a day in API calls.
The project's proxy repo, robobun, held 2,475 open pull requests on July 27, up from 1,277 on July 9. Lockwood estimates clearing that backlog alone would take roughly 86 days of continuous merging.
His $800,000 figure adds Buildkite CI time and expanded human code review on top of the original spend. It also factors in possibly $10,000 a day in continuing API credits.
The post has 453 points and 348 comments on Hacker News.
The original estimate priced the API calls that write Rust, not the humans who have to read, test, and merge what comes out. If the open PR count keeps climbing past 2,475, Lockwood's 86-day backlog estimate will look optimistic.
Each link below shares sources, entities, or timing with this story.
Shared entity: July / Shared topic / Earlier coverage / Tension
Both cover July; overlapping topics (behind, days, july); earlier July coverage from 2026-07-19.
Shared entities / Earlier coverage / Tension
Both cover July, PRs; earlier July coverage from 2026-07-23; pushes against this story (against).
Both cover July, PRs; earlier July coverage from 2026-07-21; pushes against this story (contradicts).
Both cover July, PRs; earlier July coverage from 2026-04-28; pushes against this story (but).
Shared entity: July / Shared topic / Earlier coverage / Tension
Both cover July; overlapping topics (days, july); earlier July coverage from 2026-07-24.
Both cover July; overlapping topics (call, july); earlier July coverage from 2026-07-22.
Both cover July; overlapping topics (behind, call); earlier July coverage from 2026-07-09.
Shared entities / Earlier coverage
Both cover July, PRs; earlier July coverage from 2026-07-25.