13 ms·

Bun is moving towards rust but does this also help bun's compilation times? https://ziggit.dev/t/bun-s-zig-fork-got-4x-faster-compilation-times/15183 https://z

Bun is moving towards rust but does this also help bun's compilation times? https://ziggit.dev/t/bun-s-zig-fork-got-4x-faster-compilation-times/15183 https://ziggit.dev/t/bun-s-zig-fork-got-4x-faster-compilatio...

androiddrew 4mo ago
I think bun is moving to rust because Anthropic owns it and the devs there like rust. So why would they invest in another implementation? Sad to see a good zig example go, but as soon as Anthropic bought it I wrote the project off.
- xorgun 4mo ago
  [dead]
- pylotlight 4mo ago
  Just plain incorrect.. please stop spouting this nonsense, this is not the reason whatsoever.
  - amazingamazing 4mo ago
    What is the reason?
    - galangalalgol 4mo ago
      I am not aure either, but bun wasn't using normal zig and there was drama about upstreaming. Combine that with anthropics desire to show they can help rewrite everything in rust and that probably accounts for some of it.
    - insanitybit 4mo ago
      The explicitly stated reason is that they ran into too many segfaults and it was slowing down development velocity. That said, I hope that Zig posts won't be plagued by "but the bun thing" like this in the near future.
ulbu 4mo ago
bun seems to be committed to slop rust already. so, with their ethic, maybe we should just disassociate them from zig and let them go realize their slop dreams? zig is on its way to improving compilation times in its own pace and does so for the benefit of the project and everyone involved, so what is left to care for about bun by anthropic’s past?
- jgalt212 4mo ago
  I bet they'll ultimately reverse course on this, or the there will be a bun / zig fork becomes the de facto bun. Despite what the influencers say, I'm convinced you cannot vibe code a conversion this big. It will need a ton of human intervention. And for brand narrative reasons, Anthropic won't commit to such a path.
  - galangalalgol 4mo ago
    It depends on how thorough the test infrastructure is I think. Something like curl with its immaculate tests could probably get autonomously ported if you threw infinite tokens at it because you have deterministically defined what finished looks like. But I think you are likely right in this case.
- NewsaHackO 4mo ago
  > bun seems to be committed to slop rust already. so, with their ethic, maybe we should just disassociate them from zig and let them go realize their slop dreams? Closing your eyes and pretending a problem does not exist is the a good solution. The fact of the matter is one of the biggest projects that used Zig thought that the devX was so bad that they opted to rewrite their entire 1M LOC project into a different language. This is a nightmare scenario for most companies, and will motivate similar sized companies/project to pick another language that will not require this than to risk using Zig. Also, Zig’s flippant attitude about Bun’s request (among other viewpoints) only further adds to why bigger projects would want to stay away from Zig.
  - araoz 4mo ago
kristoff_it 4mo ago
Bun has de-facto refused to use incremental compilation in Zig for ages. It got to the point where Jarred somehow seems to have forgotten that the feature exists. In any case Bun has already committed to the Rust slop switch, so it doesn't matter anymore.
teabee89 4mo ago
Somebody should revive the zig version of bun and call it banh as in the vietnamese banh mi sandwich :)

androiddrew 4mo ago

I think bun is moving to rust because Anthropic owns it and the devs there like rust. So why would they invest in another implementation? Sad to see a good zig example go, but as soon as Anthropic bought it I wrote the project off.

xorgun 4mo ago
[dead]
pylotlight 4mo ago
Just plain incorrect.. please stop spouting this nonsense, this is not the reason whatsoever.
- amazingamazing 4mo ago
  What is the reason?
  - galangalalgol 4mo ago
    I am not aure either, but bun wasn't using normal zig and there was drama about upstreaming. Combine that with anthropics desire to show they can help rewrite everything in rust and that probably accounts for some of it.
  - insanitybit 4mo ago
    The explicitly stated reason is that they ran into too many segfaults and it was slowing down development velocity. That said, I hope that Zig posts won't be plagued by "but the bun thing" like this in the near future.

ulbu 4mo ago

bun seems to be committed to slop rust already. so, with their ethic, maybe we should just disassociate them from zig and let them go realize their slop dreams? zig is on its way to improving compilation times in its own pace and does so for the benefit of the project and everyone involved, so what is left to care for about bun by anthropic’s past?

jgalt212 4mo ago
I bet they'll ultimately reverse course on this, or the there will be a bun / zig fork becomes the de facto bun. Despite what the influencers say, I'm convinced you cannot vibe code a conversion this big. It will need a ton of human intervention. And for brand narrative reasons, Anthropic won't commit to such a path.
- galangalalgol 4mo ago
  It depends on how thorough the test infrastructure is I think. Something like curl with its immaculate tests could probably get autonomously ported if you threw infinite tokens at it because you have deterministically defined what finished looks like. But I think you are likely right in this case.
NewsaHackO 4mo ago
> bun seems to be committed to slop rust already. so, with their ethic, maybe we should just disassociate them from zig and let them go realize their slop dreams? Closing your eyes and pretending a problem does not exist is the a good solution. The fact of the matter is one of the biggest projects that used Zig thought that the devX was so bad that they opted to rewrite their entire 1M LOC project into a different language. This is a nightmare scenario for most companies, and will motivate similar sized companies/project to pick another language that will not require this than to risk using Zig. Also, Zig’s flippant attitude about Bun’s request (among other viewpoints) only further adds to why bigger projects would want to stay away from Zig.
- araoz 4mo ago

kristoff_it 4mo ago

Bun has de-facto refused to use incremental compilation in Zig for ages. It got to the point where Jarred somehow seems to have forgotten that the feature exists. In any case Bun has already committed to the Rust slop switch, so it doesn't matter anymore.

teabee89 4mo ago

Somebody should revive the zig version of bun and call it banh as in the vietnamese banh mi sandwich :)