by kristoff_it
3 subcomments
- To me the most interesting fact about this fork is that it has proven that Bun could have had fast builds all along.
To be fair, there are caveats still in place today: Zig incremental compilation does not yet support aarch64 and only the linux linker supports binary patching, but it's just a matter of time before all major platforms are conquered.
- > To this end, LLMs will be used extensively to deslop...
So we're using LLMs to clean up the code that LLMs ruined in the first place? We’ve reached peak tech in 2026.
by robertlagrant
6 subcomments
- > I’ve cut over 11,000 lines of completely dead code from Bun. I can’t think of another project whose codebase was so neglected as to reach 11K lines of dead code. I’ve also rewritten and modernized parts of the codebase, trying to rely more on Zig’s stdlib. In the process, countless bugs have also been fixed.
This is astonishing. Is anyone else surprised at this dead code figure? Is it a feature of large projects I've just never noticed?
by softwaredoug
2 subcomments
- This effort makes me think of the tick-tock oscillation between features and code stewardship I’ve experienced on every agent heavy coding project
Tick: go hard after features, build a correct and extremely messy version
Tock: digest what was done, deslopify, improve project aspects that go beyond feature correctness: performance, maintainability, general fragility / sensitivity to change
My experience is spending a day vibe coding a working application. Then a week unslopifying it to make it a viable software project that can sustainably accept more features without the house of cards collapsing.
You sort of did this pre-AI, but then the professional human coder had a stronger mental model of the system, and IMO was going slower that the switch from tick to tock wasn’t as jarring
- > To that end, I’ve cut over 11,000 lines of completely dead code from Bun. I can’t think of another project whose codebase was so neglected as to reach 11K lines of dead code.
How long has this person been programming?
by christophilus
2 subcomments
- Bun, but managed by someone who values code quality? Sign me up. It’s a Herculean task, though.
- This is what I like to call performative performance programming. I _LOVE_ performance as much as the next guy. And build times should be as close to 0 seconds as possible.
But this is approaching diminishing returns and I guarantee that your CURRENT bottleneck is not build times.
- Why is there so much buzz around bun? Can't we just go back to node + npm + vitest + vite?
- > I don’t think any human should sacrifice their sanity untangling this mess of 600K lines of slop code. For that reason, I will not be accepting any human-coded contributions until I deem the project to be in a sane enough shape.
Very funny to see a "no humans allowed" contribution policy, and the absurd part is that the rationale actually makes sense.
I'm interested to see where this goes. Is it possible to "deslop" something of this magnitude?
by evertheylen
0 subcomment
- Also highly relevant project: Cruller, also uses the pre-rewrite Bun codebase but focuses only on the runtime part for production.
Link: https://ziggit.dev/t/cruller-buns-zig-runtime-continued-on-z...
Discussed on HN: https://news.ycombinator.com/item?id=49017344
- Should have called it Bunz!
- I'd also like to see a (kind of) opposite approach: a fork of zig using only AI contributions. This is more as conceptual art or an experiment, rather than because I strongly support AI. But it would be fun to see how the two projects evolved....
- I maybe am reading too much into this, but it's weird to me that a zig lead would be posting about an AI-only project despite zig's stance on AI. Maybe zig's official stance isn't that well supported in their own community.
- Performative programming
- what is this obsession with bun and js in general? with all this vibe coding why not fix the reasons we needed js in the first place
- >11K deadcode.
How did they end up there? There was another project trying to savage what is left of Zig Bun and turned it into a smaller runtime. I hope may be the project could both work together.
by 999900000999
0 subcomment
- Here’s my idea.
DinnerRoll
Bun in D!
If someone with an MBA wants to raise capital we can start next Tuesday!
- > modern Zig
Do they mean more modern than the latest tagged release, 0.16.0, released April 14, 2026?
- Very interesting, but without an ecosystem I doubt this person can keep maintaining it long term. Bun users who don't care about slop will continue to use Bun, those who care will go back to Node.js, and there isn't much left for this project. It is a gigantic task to maintain a JS runtime and add features.
- Wouldn't be JavaScript without a new flavor of the month runtime or framework.
by searealist
0 subcomment
- Thank god this is written in modern Zig and not Zig88.
- And people think there won't be enough demand for AI companies to IPO.
All they have to do is start an LLM-driven bun fight.
- We are soooo back
- jackie chan meme
by sausagefest
0 subcomment
- Stop forking bun.
Use regular Node.js.
Then making something people want.
- Now that no one cares about JS frontend framework, we moved the drama over to JS tooling written in other languages.
One reason I find deno nicer is that the node creator is solid isn't a slopperoo yapping about LLM induced quasi-productivity.
by saurabhmudradi
0 subcomment
- This just made the bun team work harder on the weekends lol
- [dead]
by rishav_sharan
2 subcomments
- [flagged]
- saw another project based on pre-rust bun and this is another one
never use bun and sometimes this make me wonder, are we enter a phase the supply way > requirement or people just build stuffs and not care serious usage anymore?
As a software engineer these days, I can't say i do not use Agent to help work done, but i am really a bit of tired to see so much solutions while not talk about what problem they are trying to really solve
- > Bun is the quintessential AI slop project at this point.
To call the Bun rewrite "quintessential slop" is all I need to know to not take this person or their project seriously.
Hacker News