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.

▲

CrimsonRain a day ago | parent [-]

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.

▲

jdiff a day ago | parent [-]

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.

▲

CrimsonRain 17 hours ago | parent [-]

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.

	▲	jdiff 16 hours ago \| parent [-]
		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.