Comment by simonklee

1 day ago

Say what you want, but for people building products on Bun, this is bad news for the foreseeable future.

I am genuinely speechless.

I don't understand the rationale behind how any project, especially of this magnitude, can seriously build something stable this way.

My consolation - and it could be pure cope - is that at least I am in the same boat as a huge company like Anthropic, and they surely wouldn't be stupid enough to also build their cli tools around something that they saw as risky.

feelsbadman.

I guess that the next release of Claude Code will use that runtime.

No later than next week.

This is bad for anyone building on Zig.

  • Cue the clueless CEOs of zig shops (I don't know many, but still):

    "Rust is faster and safer! Port it! If you don't do it, I'll do it myself, because AI can do everything a programmer can, including the stuff you don't want to do. Ship it!"

    • What serious zig shops exist are generally run by actual engineers. Check out tigerbeetle if you want a good example.

  • Why would it be? There is projects like Roc that did the opposite, they went from rust to zig, as they (had to) use lots of unsafe rust. And before you ask, no it was not an AI generated rewrite.

    • that is the point. rewrite is fine when - you take your sweet time doing that - you still know full well the codebase

      that will ensure the new codebase can still be well understood and can continue to grow in foreseeable future

      or you can just vibe the whole experience if it is a legacy project with all the specs and edge cases known.

      since bun rewrite is neither of the case, it will be a crapfest soon enough.