5 ms·

> 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 l

> 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 2mo ago
> 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 2mo ago
  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 2mo ago
    > 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 2mo ago
      None of that makes any sense whatsoever.
      - orf 2mo ago
        Pretty simple: it shipped to the owner.
        dgellow 2mo ago
        Aka: internal beta
        orf 2mo ago
        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 2mo ago
        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
dvt 2mo ago
> 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 2mo ago
  > 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 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.
  - rcxdude 2mo ago
    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 2mo ago
      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 2mo ago
      Isn't supposed to be faster with LLMs?
      - rcxdude 2mo ago
        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.
vintermann 2mo ago
I guess Claude too gets stuck on "wait! Let me think this through..." eventually.
petersumskas 2mo ago
Chris Newman fan? You should have lead with “What is it now?”
CaramelRaisins 1mo ago
(It was shipped.)

re-thc 2mo ago

> 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 2mo ago
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 2mo ago
  > 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 2mo ago
    None of that makes any sense whatsoever.
    - orf 2mo ago
      Pretty simple: it shipped to the owner.
      - dgellow 2mo ago
        Aka: internal beta
        orf 2mo ago
        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 2mo ago
        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

dvt 2mo ago

> 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 2mo ago
> 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 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.
- rcxdude 2mo ago
  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 2mo ago
    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 2mo ago
    Isn't supposed to be faster with LLMs?
    - rcxdude 2mo ago
      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.

vintermann 2mo ago

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

petersumskas 2mo ago

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

CaramelRaisins 1mo ago

(It was shipped.)