8 ms·

This post doesn’t make sense. It was rewritten in Rust. The rewrite itself is complete (no more Zig). Various people have claimed that Bun in Zig had a lot of

by muglug 2mo ago

This post doesn’t make sense. It was rewritten in Rust. The rewrite itself is complete (no more Zig). Various people have claimed that Bun in Zig had a lot of tech debt. If they’re to be believed, it seems natural to assume the rewrite does, too. Perhaps all this activity is paying down some of that debt.

abalashov 2mo ago
> Perhaps all this activity is paying down some of that debt. Perhaps. But were that the case, one would think they'd be quite eager to say so.
- muglug 2mo ago
  Maybe they will! Are you expecting them to live-tweet their work or something?
  - tough 2mo ago
    jared was OK making this rewrite as an experiment branch in the public why shouldnt upcoming work be as public as the rewrite itself was?
    - skeledrew 2mo ago
      You may continue to hold your breath. You may die as a result. The maintainers continue to do what they want regardless.
      - tough 2mo ago
        I do not really care, just pointing where people's assumptions might be coming from. The beauty of FOSS tho is Jarred owes the community nothing, and anyone can fork bun previous to migration and keep maintaining it on zig if they so wish. long live open source
  - abalashov 2mo ago
    Based on the way they live-tweeted (as it were) their rewrite and their other publicity stunts? Yes, actually.
rk06 2mo ago
bun in zig was used by many companies. some were using it in prod. how many of those are using it in prod? none, because bun in rust is not released yet. Hence, the author concludes that rust rewrite is not complete as bun in rust is not released yet. I agree with author's POV.
- davidgtonge 2mo ago
  The rust version is being used by Claude Code though - which is a fairly large product! I was hoping for more push back against https://bun.com/blog/bun-in-rust https://bun.com/blog/bun-in-rust - which is pretty thorough and has some decent arguments and reasoning for why they did the rewrite.
  - reactordev 2mo ago
    I think they meant “released and available for use” rather than just out in the wild.
    - thevinter 2mo ago
      It is available for use: `bun upgrade --canary`
      - strobe 2mo ago
        it doesn't imply that lot legacy apps won't crash in prod when it will be actually released. Cool that some complex app is working but is nothing proving that everything will be fine when everyone will try to upgrade.
  - nullsanity 2mo ago
    Yeah, but it's a TUI that has more bugs and worse performance than any other TUI in history. It's not like we'd notice a user after free.
  - flohofwoe 2mo ago
    How much of the Bun/Node API surface does Claude Code actually use though? Conceptually it's a relatively simple TUI application.
virajk_31 2mo ago
Author kept "going" in title because there has been no minor/major release in last two months which unusual for this project if you review the older releases.
- muglug 2mo ago
  A major rewrite in another language is also unusual for this project. It took TypeScript a year to go from announcing tsgo to releasing TypeScript 7.0. That work was done in parallel; here the work is being done serially — and it’s likely to take much less than a year for a new release.
  - virajk_31 2mo ago
    Yes, its because Anthropic took over and wanted to showcase their LLM capabilities by porting such a complex codebas.
    - taormina 2mo ago
      Everyone’s point is “they have everything to gain by lying about being more done then they are” and “the claims seem at least a bit full of shit”.
  - chmod775 2mo ago
    > It took TypeScript a year to go from announcing tsgo to releasing TypeScript 7.0. These are not comparable at all. The bun "rewrite" really is more of a translation of a software that is mainly dogfooded, created with an at best loose regard for a wider ecosystem. TypeScript 7.0. by comparison is not just a translation from one language to another. It's a true rewrite that at the same time has to consider a massive existing ecosystem (which needs to catch up first or you risk fragmenting it). Plus you might as well consider 6.x part of the effort, since that was the stepping-stone. Also where bun really is just a runtime implemented with a bunch of glue code plus supporting tooling, TypeScript is much more complex. Change one part of TypeScript and you can get cascading issues somewhere else in the compiler easily. Change something in Bun and you'll likely just break some discrete part.
cowl 2mo ago
tech dept is not a problem. to paraphrase captain Jack sparrow. "even if it were the most indepted working software project, IT WORKED". On the other side of the medal we have a rewritten software that although it's trumpeted for it's rewrite speed, it is not showing the same Release speed as the manualy written, "tech dept ridden" old one.
pizza234 2mo ago
> This post doesn’t make sense The author's assumption is that a rewrite is not just a mechanical translation of code - it's also a state of stability. And no release, for the author (I agree) means no stability. It's like a developer who says that after a week of work, a feature is 90% ready, but the other 10% is still not ready (for release) after months.
Aurornis 2mo ago
> Various people have claimed that Bun in Zig had a lot of tech debt. If they’re to be believed, This is one of the funnier takes on the rewrite. Bun was held up as a flagship Zig project for years. Then they chose to rewrite in Rust and everyone up to the Zig author has suddenly switched to claiming that Bun was terrible code all along.
- IsTom 2mo ago
  If what they're claiming is true then what were they supposed to do? Go "Hey guys, it's the biggest project in Zig and it sucks, don't look at it"? Not exactly a good PR move.

by muglug 2mo ago

abalashov 2mo ago

> Perhaps all this activity is paying down some of that debt. Perhaps. But were that the case, one would think they'd be quite eager to say so.

muglug 2mo ago
Maybe they will! Are you expecting them to live-tweet their work or something?
- tough 2mo ago
  jared was OK making this rewrite as an experiment branch in the public why shouldnt upcoming work be as public as the rewrite itself was?
  - skeledrew 2mo ago
    You may continue to hold your breath. You may die as a result. The maintainers continue to do what they want regardless.
    - tough 2mo ago
      I do not really care, just pointing where people's assumptions might be coming from. The beauty of FOSS tho is Jarred owes the community nothing, and anyone can fork bun previous to migration and keep maintaining it on zig if they so wish. long live open source
- abalashov 2mo ago
  Based on the way they live-tweeted (as it were) their rewrite and their other publicity stunts? Yes, actually.

rk06 2mo ago

bun in zig was used by many companies. some were using it in prod. how many of those are using it in prod? none, because bun in rust is not released yet. Hence, the author concludes that rust rewrite is not complete as bun in rust is not released yet. I agree with author's POV.

davidgtonge 2mo ago
The rust version is being used by Claude Code though - which is a fairly large product! I was hoping for more push back against https://bun.com/blog/bun-in-rust https://bun.com/blog/bun-in-rust - which is pretty thorough and has some decent arguments and reasoning for why they did the rewrite.
- reactordev 2mo ago
  I think they meant “released and available for use” rather than just out in the wild.
  - thevinter 2mo ago
    It is available for use: `bun upgrade --canary`
    - strobe 2mo ago
      it doesn't imply that lot legacy apps won't crash in prod when it will be actually released. Cool that some complex app is working but is nothing proving that everything will be fine when everyone will try to upgrade.
- nullsanity 2mo ago
  Yeah, but it's a TUI that has more bugs and worse performance than any other TUI in history. It's not like we'd notice a user after free.
- flohofwoe 2mo ago
  How much of the Bun/Node API surface does Claude Code actually use though? Conceptually it's a relatively simple TUI application.

virajk_31 2mo ago

Author kept "going" in title because there has been no minor/major release in last two months which unusual for this project if you review the older releases.

muglug 2mo ago
A major rewrite in another language is also unusual for this project. It took TypeScript a year to go from announcing tsgo to releasing TypeScript 7.0. That work was done in parallel; here the work is being done serially — and it’s likely to take much less than a year for a new release.
- virajk_31 2mo ago
  Yes, its because Anthropic took over and wanted to showcase their LLM capabilities by porting such a complex codebas.
  - taormina 2mo ago
    Everyone’s point is “they have everything to gain by lying about being more done then they are” and “the claims seem at least a bit full of shit”.
- chmod775 2mo ago
  > It took TypeScript a year to go from announcing tsgo to releasing TypeScript 7.0. These are not comparable at all. The bun "rewrite" really is more of a translation of a software that is mainly dogfooded, created with an at best loose regard for a wider ecosystem. TypeScript 7.0. by comparison is not just a translation from one language to another. It's a true rewrite that at the same time has to consider a massive existing ecosystem (which needs to catch up first or you risk fragmenting it). Plus you might as well consider 6.x part of the effort, since that was the stepping-stone. Also where bun really is just a runtime implemented with a bunch of glue code plus supporting tooling, TypeScript is much more complex. Change one part of TypeScript and you can get cascading issues somewhere else in the compiler easily. Change something in Bun and you'll likely just break some discrete part.

cowl 2mo ago

tech dept is not a problem. to paraphrase captain Jack sparrow. "even if it were the most indepted working software project, IT WORKED". On the other side of the medal we have a rewritten software that although it's trumpeted for it's rewrite speed, it is not showing the same Release speed as the manualy written, "tech dept ridden" old one.

pizza234 2mo ago

> This post doesn’t make sense The author's assumption is that a rewrite is not just a mechanical translation of code - it's also a state of stability. And no release, for the author (I agree) means no stability. It's like a developer who says that after a week of work, a feature is 90% ready, but the other 10% is still not ready (for release) after months.

Aurornis 2mo ago

> Various people have claimed that Bun in Zig had a lot of tech debt. If they’re to be believed, This is one of the funnier takes on the rewrite. Bun was held up as a flagship Zig project for years. Then they chose to rewrite in Rust and everyone up to the Zig author has suddenly switched to claiming that Bun was terrible code all along.

IsTom 2mo ago
If what they're claiming is true then what were they supposed to do? Go "Hey guys, it's the biggest project in Zig and it sucks, don't look at it"? Not exactly a good PR move.