4 ms·

they're referring to the changes they tried to upstream to zig.

• tomjakubowski 5mo ago
  To be fair, I don't know if the Bun team ever did try to upstream it. In their Twitter thread announcing their vibe-coded fork of the Zig compiler, they said they wouldn't bother trying to upstream their changes because of Zig's policy banning LLM-authored contributions. Still probably a calculated political move to cut ties with Zig and muster community support for a Rust rewrite. https://x.com/bunjavascript/status/2048428104893542781 https://x.com/bunjavascript/status/2048428104893542781
  • happymellon 5mo ago
    They did try upstreaming to Zig, but it was rejected for already being implemented not because it was vide coded. https://ziggit.dev/t/bun-s-zig-fork-got-4x-faster-compilation-times/15183/19?u=andrewrk https://ziggit.dev/t/bun-s-zig-fork-got-4x-faster-compilatio... Bun were so excited about their 4x speed improvement that they missed that Zig had already implemented it, plus other optimisations that were far larger.
    • gpm 4mo ago
      > They did try upstreaming to Zig Nothing in your link supports this assertion. Lots of things in your link support the exact opposite in fact, that the Bun team explicitly chose not to attempt to upstream the changes.
• happymellon 5mo ago
  The changes submitted to zig were rejected because they were off an old fork and had already been implemented. They may have been rejected for being vibe coded if they were original, but they were rejected for being pointless. The rust rewrite was because Bun was butt hurt that they didn't actually help.