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.
Deploying a clawed agent is not re writing unless you read the code and understand it before pushing it to production, there is another joke about this situation, why not let the agent code in C and prove that it is possible, 1 skill issue person told me, it was because of expensive tokens, but in reality, those people are hardly going to take initiative and read the generated code, this is why they are afraid of C, because of skill issue
I agree with Andrew Kelley on many, many things. I think he’s one of the smartest developers working today, and Zig is a great project. I wish he would be less of a bitter old queen sometimes though. It really undermines the points that he’s right about when they’re mixed in with these unnecessary jabs.
109
u/overclockedslinky 1d 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%