4 ms·

But one of the reasons they switched was because the compiler upstream for the original language they used, Zig, wouldn't accept slop contributions they wanted

But one of the reasons they switched was because the compiler upstream for the original language they used, Zig, wouldn't accept slop contributions they wanted to make for Bun perf. What will they do when they need to try to push a slop contribution upstream to rust? At this point they will probably just fork yet again and maintain some vibe compiler.

whattheheckheck 5mo ago
They should make FullstackLang. It compiles English in .md to machine code that can directly run on the specialized hardware it designs for it that you have to 3d print at runtime. Every program gets its own custom hardware. Composability and reuse be damned. Pay the token masters for every thought you have
ares623 5mo ago
Huh. I wonder if the original intent was to merge an AI generated PR to a high-profile project like Zig. It makes the headlines and generates hype. But that went embarassingly bad for them so they had "port Bun to Rust" as a backup.
noobermin 5mo ago
Is there a citation for this? This was my suspicion but it's quite amazing if this was the actual reason for the bun spectacle
- sheept 5mo ago
  No, they've explicitly denied it.[0] However, they do regularly dig at how much faster their fork is[1][2] that they can't merge because of Zig's AI policy. [0]: https://x.com/jarredsumner/status/2051600118886138262 https://x.com/jarredsumner/status/2051600118886138262 [1]: https://x.com/bunjavascript/status/2048427636414923250 https://x.com/bunjavascript/status/2048427636414923250 [2]: https://x.com/jarredsumner/status/2053050239423312035 https://x.com/jarredsumner/status/2053050239423312035