> 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.
I know nothing about the drama here other than what's in the blog post, but these feel more like unnecessarily public personal attacks which don't really reflect well:
- a stinky manager. Poor communication, unrealistic expectations, low empathy, no experience. Just a total shit show, from an employment perspective
- already writing slop well before he had access to LLMs
- their vague "sell some cloud something" business plan was a farce
> I actually don't have any personal criticisms of Jarred.
was the cherry on top.
I also know nothing of the drama, but what I picked up from the first blog post was that even with access to near unlimited funds and unreleased god-tier coding llms from a trillion dollar AI corporation it was apparently impossible to fix a backlog of bugs in Zig code but it was possible to fix them by automatically doing a rewrite in rust.
I can see why that might feel like an existential attack on Zig even if starts with a bit about how great Zig is.
So pointing out that the zig code was full of bugs because the author was doing weird stuff and ignoring advice, couldn't hire/retain any good Zig devs because he mismanaged people and is the kind of guy to do a full rewrite because that's more interesting than fixing bugs or learning the old tools feels like stuff he'd want out there in the public domain.