221–230 of 757 posts
Earlier quoted context omitted.
4) It's led by an emotionally unintelligent individual who will personally attack you for choosing alternative products.
Like Linus?
There are astute comments about the post's tone elsewhere in this thread[0] But this killed my hopes for Zig. The drama is fun, and Andrew is maybe even admirable in his earnest, but this just isn't the kind of professionalism needed for a serious project. I know that's boring and uninspired, but that's what I want my tech stack and it's management to be. Also, maybe Jarred was a net negative, but bun was also a real…
I don't immediately see how much the seriousness of the project is related to the language the author chose in their personal blog post. It's similar to saying that Linux could not have become a serious project because of the way Linus communicated in his emails.
Earlier quoted context omitted.
Even if you “rely on countless unsafe blocks”, unsafe is additive, it gives access to additional APIs which are not checked. It does not disable affine types, the borrow checker, or send/sync traits. Unless the entire codebase is unsafe (e.g. fresh out of c2rust) it’s very hard to not have more guarantees. And because unsafe is generally highly local or localizable reasoning (conventionally backed by safety justifica…
For 99.99% of cases, you're reading and writing this under an operating system whose kernel is written in a language without send/sync, and inside a browser that also largely written in languages without send/sync, because those systems are fundamentally well designed. So instead of fixing the bugs and rethinking the architecture, the author of Bun decided to transpile almost the entire codebase from Zig to Rust with…
Earlier quoted context omitted.
It's kind of strange to not engage with any of the points made in the article. Unlike you, I don't think the post makes them look childish at all. I think it raises a lot of valid points and makes me want to use Zig more.
Do you have bias? I'm not saying I don't have some hidden bias but I have no skin in the game. I don't use Bun or Zig or plan to. My reflection comes after reading Jarred's post yesterday, which I found interesting, and then Andrew's today. I just pasted this article into an LLM to understand the tone and the summary is: > The overall tone is deeply personal, cathartic, biting, and polemical, with flashes of humor an…
Earlier quoted context omitted.
I’m reminded of the hierarchy of controls in machine safety. If you can’t eliminate the hazard, or substitute a less hazardous thing, then engineering out the hazard (like Rust did) is preferable to a procedural control (“git gud at engineering”).
C/C++ does not care and they’re currently the language for foundational work (OS, platforms, and libraries). Python and Java does not care, they will just throw runtime exceptions and crash. Rust care, but they don’t play well with the rest of the world.
When I read about the bun rewrite I thought no sh*t, those are the exactly the types of bugs I would expect when doing a line by line rewrite of a program in a GC language to memory managed. I was unimpressed with the engineering from the blog, and I'm not surprised to read andrew say they claimed no fuzz testing. I know someone who interviewed at bun when it was less than 10 people (around 5 he said). Allegedly jare…
Earlier quoted context omitted.
> It's insane to me that Andrew thinks this post will somehow exonerate Zig when it really just makes them look childish. Antirez made a post equivalent to: you'd be a fool not to use AI to increase test coverage. Zig on the other hand has embarrassingly low test coverage given its adoption and time in development. Their stance on AI is completely childish. They could benefit massively from it, yet refuse to even con…
Childish or no, anti-AI sentiment is ubiquitous and growing. From a PR perspective there’s a lot to gain in the short term by picking the “anti-AI” lane. And you can always change your mind later.
Is the bun rewrite actually done? There's no tag for the release, and as it stands robobun has almost 1.3k open PRs on the repo: https://github.com/oven-sh/bun/pulls/robobun It doesn't look done. And it looks like work on the rewrite began in early may: https://github.com/oven-sh/bun/commit/46d3bc29f270fa881dd573... So... its more like a 2 month rewrite that is definitely not done yet????
From the rewrite to Rust article: > Bun v1.3.14 was the last version of Bun written in Zig. Bun v1.4.0 will be the first version of Bun written in Rust. It's available in canary now. It's also been shipping with Claude Code since June 17th.