> Bun · Rust codebase audit · May 21, 2026 · AI generated
nice of them to be up-front about it, I guess.
the port is AI slop, littered with 13k unsafe blocks.
and this blog post is more AI slop, claiming to present a "plan" for how to reduce that number.
why should anyone trust anything they output? all they're trying to do is cover up their slop with more slop.
if you're cleaning your house, and the dirt can't all fit under one rug, the obvious solution is to buy another rug.
I trust their judgement to do the right thing.
I don’t understand the overreaction since this is a parallel development.
If it turns out to be better than make it default. Bugs get fixed it’s not like their zig version didn’t have issues before.
Anthropic has a serious savior complex (when it is actually about total control) and believe that you should not run your own models locally and they do not care about you and I.
This Bun Zig to Rust rewrite is great content for them and for their IPO prospectus, but it isn't performative in the sense that it is fake. (It is real with terrible code.)
What this really means is that it gives the green light to managers and everyone else to use Claude to do massive rewrites; even when it produces hundreds of thousands of lines of slop.
Unless comprehension debt is what you want.
You do not have the same amount of token-spend as the Bun team does.
> I trust their judgement to do the right thing.
They will do the "right thing" for their investors (and soon Wall Street).
That's good to see. I was getting a bit worried but now feeling better about it.
Porting to a safe language without the safety features.
Look no further than their owner for the reason, unless it is merely a coincidence this only happened after a change in ownership…
We're running forward without any idea of how we can get agents to write code that is even remotely safe or secure. It _will_ blow up with increasingly large blast radiuses.