new | show | ask | jobs Github

frail_figure 5 days ago

> how have the last few months not looked good for Bun, exactly?

The article answers this. hint: they're not shipping.

> I get it, you don't like AI or you like Zig over Rust, or whatever

The article doesn't argue for either of these. hint: it's arguing that the team is not shipping.

> Terrible argument, and not really an argument at all.

It's an argument for the devs not shipping

> I agree, so look at the code and point out what's wrong with it.

It's not being shipped.

Hope that helps.

▲ re-thc 5 days ago | parent | next [-]

> The article answers this. hint: they're not shipping.

They're shipping though.

Claude Code and many others use it. There's just not been a "public" release.

▲

aureate 5 days ago | parent [-]

In other words, it hasn't shipped.

The bun rewrite is looked to as proof that this sort of full-throttle vibecoding is the future of software development, at least for large porting projects like this one, and for many people on this site that is a high stakes question.

To prove that, a proper release is needed, and the Bun community needs to adopt it. There's a huge partisan eagerness to declare the Claude Code release or anecdotal experiences on the canary as victory, but the viability of 1.4 hasn't been demonstrated until it has been released and adopted by the bulk of the community.

There isn't actually any hurry on that. Nobody needs Bun 1.4 tomorrow. It's Jarred that keeps saying it'll be released tomorrow, while the code churns at an astonishing rate (see below). People with a skeptical outlook will inevitably suspect that he doesn't have confidence in the release and is struggling to acquire it.

Github insights for the last week:

> Excluding merges, 57 authors have pushed 349 commits to main and 6892 commits to all branches.

> On main, 2026 files have changed and there have been 189,502 additions and 133,836 deletions

▲

re-thc 4 days ago | parent [-]

> The bun rewrite is looked to as proof that this sort of full-throttle vibecoding is the future of software development

To who? You?

> To prove that, a proper release is needed

For who? Who is trying to prove what?

> It's Jarred that keeps saying it'll be released tomorrow

There's no official blog... he's just rambling on x?

> Github insights for the last week

That's the problem with the rest of your post. Bun is no longer VC-fueled open source project. It got sold to Anthropic.

> There's a huge partisan eagerness to declare the Claude Code release

Hence there isn't. The Claude Code release is for its own use.

▲

aureate 4 days ago | parent [-]

None of that makes any sense whatsoever.

▲

orf 4 days ago | parent [-]

Pretty simple: it shipped to the owner.

▲

dgellow 3 days ago | parent [-]

Aka: internal beta

▲

orf 3 days ago | parent [-]

Claude code is for sure the most widely used bun application. So the majority of bun users are using it.

That’s not what I’d call an internal beta?

	▲	dgellow 3 days ago \| parent [-]
		Sure but that’s how you beta test a runtime, by using it in a codebase you control. Claude is publicly released and used widely, that’s still only a single codebase

▲ vintermann 4 days ago | parent | prev | next [-]

I guess Claude too gets stuck on "wait! Let me think this through..." eventually.

▲ petersumskas 4 days ago | parent | prev | next [-]

Chris Newman fan?

You should have lead with “What is it now?”

▲ dvt 5 days ago | parent | prev [-]

> It's not being shipped.

What are you talking about? I'm running 1.4 canary (the Rust rewrite) right now.

    λ bun --version
    1.4.0

Hope that helps.

▲

locknitpicker 5 days ago | parent [-]

> What are you talking about?

I think GP was pointing out how bun's release cadence stalled and the project is going nowhere at the moment.

https://github.com/oven-sh/bun/releases

The project was pretty healthy up to 1.13.14, but since may they stopped shipping anything.

That's quite odd for a project that just went through a major rewrite and is lauded as being developed primarily by LLM coding assistants.

Personally I expected the release cadence was going to go through the roof, but instead it flat lined.

▲

CrimsonRain 4 days ago | parent | next [-]

So they are being more cautious and spending more time on polish after a never been done before historical massive rewrite...? Stop the press! They are not shipping as fast they used to! Omg!

▲

locknitpicker 3 days ago | parent | next [-]

> So they are being more cautious and spending more time on polish after a never been done before historical massive rewrite...?

That's not credible at all. I mean, after a major release there are tons of low-priority low-hanging fruit issues that can be quickly sorted out. That's the nature of a release process.

However, Bun stopped releasing anything. Even after lauding it's AI push,which can easily chomp through small tickets.

It's been a couple of months since the major push. I repeat: the release cadence of a mature, stable codebase as the Zig one was at 2-3 weeks. A messy rust rewrite packed with unsafe code, which is prime ground for small bugfixes and correctness fixes, led the project to grind to a halt.

No one looks good in the picture.

	▲	CrimsonRain 3 days ago \| parent [-]
		Boo hoo https://bun.com/blog/bun-v1.4

▲

dgellow 3 days ago | parent | prev [-]

Pretty sure that’s because of the backlash. So, sounds like a good thing people voiced their concerns

▲

rcxdude 4 days ago | parent | prev [-]

I wouldn't consider it particularly surprising that a big rewrite results in no new releases for a bit before the rewritten version is released.

▲

debugnik 4 days ago | parent | next [-]

Not surprising, but Jarred has been teasing "tomorrow I swear" for months and Bun keeps missing his own deadlines.

There's clearly something wrong in their confidence about Rust Bun: If it isn't ready they should have said "whenever it's done", and if it is they'd have met some deadline by now. I suspect the speed was supposed to be part of the stunt, yet they seem to have encountered the 90:90 rule.

▲

akkad33 3 days ago | parent | prev [-]

Isn't supposed to be faster with LLMs?

▲

rcxdude 3 days ago | parent [-]

The rewrite was a lot faster. Actually shaking out the bugs from the rewrite (or just getting enough confidence in the new version from use by early adopters) is probably not going to be drastically faster.

	▲	akkad33 a day ago \| parent [-]
		Then it's not a net speed gain?