Unusual tones all around in the thread here. My initial observations before reading the comments here:
* "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!
That’s fair, I should have framed it more clearly upfront. Thanks for the feedback.
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.
I totally get it and received the offering. =) Love seeing more use of io_uring too and interesting to see how that's done in Zig. Happy New Year: All the best on this and other projects.
You and OP both work for the same "High Performance AI Inference" company, you might want to disclose that.
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
Well, in that case I'm curious... Why did you think hijacking OP's stance of "Claude did rewrote lots of my original messy code" with your own opposing position of "the project itself is not AI", and getting quite offensive about it, would benefit any discussion about this 13h old project?
It's a personal project of your dear ex-colleague, mind you!
Sure, the author just happened to one-shot a project and a landing page on new year's eve. And their writing style is just coincidentally very similar to Claude's.
Its an extract of two weeks of work. And yes Claude did the website and rewrote my code that was absolutely without comments and a gigantic mess. It's an extract of the fourth attempt actually. Src4/ was the original folder. But my goal my to test the architecture applied to nats not to say I've done it without ai?
I'm also building a network server with thread-per-core and io_uring, except it's a web server, it's written in Rust, and io_uring is provided by a fork of Monoio runtime (I forked it to make it work with Windows and FreeBSD).
Upvote for Bazel. I think these days I place a lot more value on how well an ecosystem slots into Bazel/friends because monorepos are increasingly more useful and relevant.
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.
People are free to knock themselves out with Bazel if they’re into that kind of masochism, but having it as the ONLY way to build your OSS project is a big no.
The problem with "the language tooling is already a build system" is that cross-language dependency chains are a thing. The moment you need a Rust or Zig file to be regenerated and recompiled when a JSON schema or .proto file is updated, you're outside what most of those language-specific toolchains can support. This is where Bazel absolutely shines.
If all of your dependencies need to use the same build system as your project then your build system/process is defect anyway. It should be possible to invoke a foreign build system as part of your build.
Unusual tones all around in the thread here. My initial observations before reading the comments here:
* "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!
That’s fair, I should have framed it more clearly upfront. Thanks for the feedback.
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.
I totally get it and received the offering. =) Love seeing more use of io_uring too and interesting to see how that's done in Zig. Happy New Year: All the best on this and other projects.
Why use Basel instead of Zig build tools, as it’s all written in Zig anyway?
That was in the prompt.
I did a similar thing few days back just not with NATS protocol (Made it pure websocket based), and with rust. Couple of questions:
- Where did you get the machine to test your server on?
- Why did you end up going with zig?
My personal rig and Zig because I worked with it for a little more than a year. It was a fun test to do.
Anyone can buy a 9950x on Amazon or any tech store, it's consumer hardware.
Given that this entire project is a single[1] vibe-coded commit, I really doubt the author bothered buying hardware to test it.
[1]: https://github.com/bustermq/bustermq/commits/master/
Who cares whether it’s vibe coded ? As long as it’s good and well maintained over time of course.
Maybe there is a niche market for artisanal software engineering where real humans make holes in punchcards, but I would not bet.
> Who cares whether it’s vibe coded ? As long as it’s good and well maintained over time of course
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.
he’s been working on it for 2 weeks, as he said somewhere else
it's not vide coded though, that's the second time you're saying it, get lost
You and OP both work for the same "High Performance AI Inference" company, you might want to disclose that.
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
sure, i hereby disclose that he left in September
i already said in another reply that i knew him personally
Well, in that case I'm curious... Why did you think hijacking OP's stance of "Claude did rewrote lots of my original messy code" with your own opposing position of "the project itself is not AI", and getting quite offensive about it, would benefit any discussion about this 13h old project?
It's a personal project of your dear ex-colleague, mind you!
Sure, the author just happened to one-shot a project and a landing page on new year's eve. And their writing style is just coincidentally very similar to Claude's.
Who's going to buy that?
Its an extract of two weeks of work. And yes Claude did the website and rewrote my code that was absolutely without comments and a gigantic mess. It's an extract of the fourth attempt actually. Src4/ was the original folder. But my goal my to test the architecture applied to nats not to say I've done it without ai?
I'm also building a network server with thread-per-core and io_uring, except it's a web server, it's written in Rust, and io_uring is provided by a fork of Monoio runtime (I forked it to make it work with Windows and FreeBSD).
You should at least try and align the ascii flowchart in the readme on the repo.
One day Claude will do it correctly but today is not that day.
Upvote for Bazel. I think these days I place a lot more value on how well an ecosystem slots into Bazel/friends because monorepos are increasingly more useful and relevant.
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.
agreed, love Bazel + BuildBuddy
Downvote for this web site is a horror movie billboard and zig already has a build system which is zig and that's one of it's neat features.
People are free to knock themselves out with Bazel if they’re into that kind of masochism, but having it as the ONLY way to build your OSS project is a big no.
Yeah I'm never touching Bazel again. I value my sanity.
well, bazel is by far the most reliable one so I'm not sure why you're complaining
The problem with "the language tooling is already a build system" is that cross-language dependency chains are a thing. The moment you need a Rust or Zig file to be regenerated and recompiled when a JSON schema or .proto file is updated, you're outside what most of those language-specific toolchains can support. This is where Bazel absolutely shines.
Zig build system can do all that just fine though
If all of your dependencies need to use the same build system as your project then your build system/process is defect anyway. It should be possible to invoke a foreign build system as part of your build.
and it would be terrible for hermeticity and reproducibility, nix tries very hard and gets mediocre results
perhaps, just perhaps, why people go through the trouble not because they are idiots but for actual engineering reasons
Rust build system can do all that just fine though
Comparison/benchmark to other alternatives?
Wow! This entire project seem to be a big ball of AI slop.
your lack of skills doesn't mean it is (it's not)
Who would believe someone that writes something like this online?
Does it have a similar system to Jetstream? If yes, does it address the reliability issues Jetstream has been criticized about lately?
Absolutely not and will never have.