Why use Basel instead of Zig build tools, as it’s all written in Zig anyway?
Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
41–50 of 78 posts
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#42Earlier quoted context omitted.
The code of the project absolutely does look like it was done with AI lol, it’s a single commit…
Dude, when I move projects to GitHub I also often collapse everything into a single commit. 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!
Nothing individually is a good indicator of slop in itself, a human could also have written this readme full of Claud-isms and a borked ASCII schema or the code littered with idiosyncratic comments.
It's the convergent set of clues that makes the case.
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#43Earlier quoted context omitted.
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/
[flagged]
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
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#44I 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?
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).
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#45Earlier quoted context omitted.
The code of the project absolutely does look like it was done with AI lol, it’s a single commit…
Dude, when I move projects to GitHub I also often collapse everything into a single commit. 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!
And the author has admitted at least some assistance here:
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.
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#46Why use Basel instead of Zig build tools, as it’s all written in Zig anyway?
That was in the prompt.
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#47Earlier quoted context omitted.
> 1/ AIs are terrible at Zig 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 )
> zig subreddit 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. [1]: https://ziglang.org/community/
That doesn't change the fact that Claude code is definitely good enough at Zig to make vibe-coded projects.
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#48Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#49Earlier quoted context omitted.
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.
Re: Show HN: BusterMQ, Thread-per-core NATS server in Zig with io_uring
#50Earlier quoted context omitted.
Dude, when I move projects to GitHub I also often collapse everything into a single commit. 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!
And the author has admitted at least some assistance here: 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 be…
Fair point. And as what it is, not a nats replacement, certainly dont have the time to maintain that this way, a test/tech demo/fun side project that yielded super interesting results is probably the answer. As usual I'm probably way too enthusiast when I see some nice results like that and the goal here was to talk about that, but it shifted super fast. So yes Claude rewrote lots of parts, and that's what I love about it. Testing an idea happens in way less time than before, and I find that super cool.