Hacker News new | ask | show | jobs
by jdiff 13 days ago
There were very many open pull requests from the community that were all invalidated overnight for something that same community was assured was merely an experiment.

The normal process would be "hey, this experiment is going well, we've made this plan, come help us shake out the new codebase for the switchover in X time." None of that happened. There wasn't even an announcement, just a silent commit that trashed hard work from hundreds of community members.
1 comments
CrimsonRain 13 days ago
None of that is needed. Nobody benefits from all that time wasting bureaucracy/corpo speak. Bun is quick to deliver new features and bug fixes. With this change, the hope is that'll only get faster.

All those PRs can be fed thru Claude and converted to rust and then manual polish can be added.

link
jdiff 13 days ago
Bun is riddled with bugs. That's what moving fast and breaking things gets you. It gets you famously bad codebases that are nightmares to work with and slow you down over time as your sins catch up with you. Vibecoding is not enough.
link
CrimsonRain 12 days ago
Then why do you care? If target users (developers) face issues with bun, they will stop using it. Go back to Node or switch to Deno.

Bun has bugs? yes. Do they affect vast majority of users? Not really. Been using bun for about 3 years; never had an issue with it.

link
jdiff 12 days ago
Are you interested in the discussion that was taking place before you popped in or are you just here to get outraged that something you clearly identify strongly with is getting criticism for making poor choices?

"Because the discussion was interesting" is why I care.

link
CrimsonRain 12 days ago
Discussion was not interesting. It was built on speculation as facts and lies as facts.

The worst is "hey they are running proprietary fork and not open source anymore" when the code is available in plain sight. Canary build is available with one command. The stupid article made a huge stink about it without this key fact. Now they added the update but damage is done.

link
jdiff 12 days ago
No, that's not correct. That is the discussion started by the article, and the one continued in many other comment threads, even including this one far further upthread. Conversations drift over time, and this thread has evolved into a subdiscussion on the topic of the rewrite itself. If this is not what you would like to discuss, I suggest you visit the other threads.

If you would like to join us in this thread now that this misunderstanding has been corrected, please, share your thoughts on the Bun community, what the "Bun community" even is, and how it has been impacted by a sudden, unannounced rewrite.

link