- Where did you get the machine to test your server on?
- Why did you end up going with zig?
Maybe there is a niche market for artisanal software engineering where real humans make holes in punchcards, but I would not bet.
Maybe 12 hours after the first commit is a bit early to be confident about that…
> Maybe there is a niche market for artisanal software engineering where real humans make holes in punchcards, but I would not bet
Or maybe there exist a world between punchcards and evening AI slop “projects”, who knows.
> And as what it is, not a nats replacement, certainly dont have the time to maintain that this way
EDIT: and while you're at it, you might also want to work on your attitude. "you idiot", "get lost" and "you need to touch grass" are not helping any HN discussions
i already said in another reply that i knew him personally
It's a personal project of your dear ex-colleague, mind you!
because we've been discussing architecture, optimisations and benchmarks
because it's not a 13h old project
Who's going to buy that?
One day Claude will do it correctly but today is not that day.
* "wow, OSS projects are starting to have some pretty wild landing pages, guess it's not just AI logos at the top of the README anymore"
* "wow, all in one commit. was it vibe-one-shotted, curated private work that was squashed, or something in between"
* "wow, Zig is kind easy to read although I really don't want to learn another language in 2026 although I already started learning some to use libghostty"
* "wow, is Zig really this much performant than Golang at the tails"
* "weird it uses Bazel, doesn't Zig have it's own build system like Golang"
* "so who is the author? I see they made an GitHub org for this. Are they going to keep doing stuff after the commit and should I keep this in my messaging queue neurons? Is this some company or person I should follow"
* "the README has a misalignment, do I PR that?"
* "oh cool, it lets you tune memory and the dispatcher"
---
I never thought of exactly how it manifested, except about the single commit. I have started "vibe coding" much more as the capabilities really improved in the last few months, so that isn't intrinsically a trash approach.
But the "who" and the "how" and the "why" do matter, in terms of whether one should look at it for education or infotainment or as a potential tool.
Disclosure of the intention and method would be courteous to the community when we create and share these things. Otherwise we'll all have high cognitive burden with the amount of projects we'll be seeing in 2026!
I was excited about the results. The intent was to talk about performance and architecture, not to imply this was a quick or effortless project. There’s been a lot of iteration and experimentation behind it, and I should have communicated that context better as well as the use of AI for the help.
So nice to see there are good rules for Zig and that folks are using them.
Also ironically I think starting with Bazel/Buck/whatever your poison of choice is almost always a good move even if people tell you it's overkill. The easiest time to do it as at the beginning, all times after that is too hard and the marginal cost of building with it from the start is minimal.
perhaps, just perhaps, why people go through the trouble not because they are idiots but for actual engineering reasons
"Core" nats doesn't have durability. Nats jetstream is the api built on top of nats that in the main nats-server impl provides durability. Jepsen tested Nats Jetstream.
Also from your link:
> Regular NATS streams offer only best-effort delivery, but a subsystem, called JetStream, guarantees messages are delivered at least once.
The project linked here does not implement the nats jetstream api, just normal nats.
So yes, it seems its same (documented, understood) "yolo" as normal nats.
I paired with Claude and simply added nats.c to the zig buildup system for my zig project at work. It works like a charm.
you need to touch grass
I do this to avoid having to check e-mail addresses and names in commits - maybe I mistakenly made a commit from my work account etc.
After the “initial” commit making it all public, I start to work “in the open”. I see many others doing it the same way.
That is NOT a reliable indicator of slop!
https://news.ycombinator.com/item?id=46452907 https://news.ycombinator.com/item?id=46452841
There may have been less pushback if this had been expressed up front. But also, what is it ? Is it to "test the architecture applied to nats" or is it to be a fully fledged NATs replacement (as per the impression given by table at the bottom of the website) - which becomes much harder if AI has significantly re-written the authors original code (and commented it badly).
The website being AI coded I can take or leave.
It's the convergent set of clues that makes the case.
Dropping to profanities is not conducive to maintaining an environment that’s facilitating dialogue between its members.
I’ve seen you at least twice call other members here “you idiot”, “get lost”. Etc. Have a hard think as to whether you could rephrase that without the name calling, and if at worse you can’t manage to, you can always ask an LLM to do it for you.
Unlike you, I won't insult you despite you being wrong.
Claude isn't, and the zig subreddit is actually full of AI slop projects unfortunately.
And yesterday's front page Zig project was also vibe coded (though in that case the author acknowledged it: https://news.ycombinator.com/item?id=46442792)
Is the only zig community that Andrew Kelley "anti-endorses"[1]:
> I don’t have the time or energy to evaluate most Zig communities so I can neither endorse nor anti-endorse them, however, the Zig subreddit is an exception.
> It’s an awful place and I stand by my decision to permanently close it. I am unhappy that it was reopened against my will.