45 ms·

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

by 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.