51–60 of 78 posts
Earlier quoted context omitted.
[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
i already said in another reply that i knew him personally
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
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
It's a personal project of your dear ex-colleague, mind you!
* "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!
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 t…
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.
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 t…
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 am assuming the message durability guarantees lean towards YOLO rather than ACID? See also https://news.ycombinator.com/item?id=46196105
"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.
Earlier quoted context omitted.
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