Bun support is now limited and deprecated
1–10 of 646 posts
Re: Bun support is now limited and deprecated
#2Oh well, I really like using Bun and I get kinda sad about the turn they are taking after the Anthropic acquisition. I really want a good Node with batteries included, but I don't want it vibe coded.
Re: Bun support is now limited and deprecated
#3Reason #2 is purely speculative. It’s disappointing to see technical decisions being made on such grounds.
Re: Bun support is now limited and deprecated
#4Reason #2 is purely speculative. It’s disappointing to see technical decisions being made on such grounds.
What part of the recent history of vibe coded projects has not resulted in low quality, bug laden code? Dismissing this a "purely speculative" is just like dismissing the weather report as "purely speculative" when deciding what to wear in the morning.
Re: Bun support is now limited and deprecated
#5The "to vibe code or not to vibe code" holy war is now in full swing.
Re: Bun support is now limited and deprecated
#6Reason #2 is purely speculative. It’s disappointing to see technical decisions being made on such grounds.
All dependency management is speculative. You've got to hedge your bets that the dependency is reliable and fit for purpose. It is reasonable to view Bun's recent choices as increasing the risk associated with depending on it.
Re: Bun support is now limited and deprecated
#7Reason #2 is purely speculative. It’s disappointing to see technical decisions being made on such grounds.
It's a reasonable decision to not take a dependency which doesn't meet your own engineering standards. People in the JS community could learn something from that.
Re: Bun support is now limited and deprecated
#8Wow, bun support was just added in November last year (I think). That's a lot of work to throw away, but you can't argue with their reasoning.
Re: Bun support is now limited and deprecated
#9As long as Deno support is still there I'm not sure why you need anything else. It's not vibe coded slop for one.
Re: Bun support is now limited and deprecated
#10Reason #2 is purely speculative. It’s disappointing to see technical decisions being made on such grounds.
It's a common fallacy among tech folks to believe that every decision can be made from 100% deterministic grounds ("X decision will result in Y percent change"). In reality, successful decision-making often involves speculation. The speculation in question is within the bounds of reason. You may disagree, but the fact that it is speculative isn't the problem.