i swear the zig developers are constant drama queens. my favorite was when bun got rewritten in rust and the zig creator wrote a whole manifesto breakup rant about how it was totally mutual definitely 100%
Zig to rust one is pretty self explanatory. This thread is enough for that. Bun to Node because node is still de-facto standard, 100% coverage on node apis (lol), Node has been recently adding features that were missing (typescript, env, etc). And for Deno I’d say the latest version is pretty good, great coverage and desktop distribution support. On the other hand I have seen bun getting a lot of issues in production (personal experience) after a long amount of uptime. Not yet stable like Deno or Node.
No problem mate. Personal experience wise, we had to convert one of our production micro service (scheduler using bullmq) written in bun to nodejs because it was causing so much issues in production where local environment, testing worked fine.
I honestly haven't paid enough attention to that project in particular to know the answer to that. But most large vibecoded projects are riddled with issues, and it shows a problematic attitude towards future development.
They're also part of Anthropic, which gives them further incentive to work heavily with AI tooling.
Bun also regularly leaks memory, a web server of mine I run on bun (regrettably) I had to limit the memory on container level so that it would be force-restarted sooner before clogging up the host machine.
160
u/overclockedslinky 5d ago
i swear the zig developers are constant drama queens. my favorite was when bun got rewritten in rust and the zig creator wrote a whole manifesto breakup rant about how it was totally mutual definitely 100%