Hacker News Reader

Comment by vekntksijdhric | Hacker News Reader

A 13 HOUR OLD repo? no thanks

What stands out to me isn't only that the repo was made less than 20 hours ago, but that they've released from 1.0.0 to 1.0.10 since then.

But at the same time the PR numbering is much older, with 1.0.10 coming from #197. It makes me think the repository was private for some time and then made public recently. But still -- 10 releases in a few hours isn't a stability signal. Especially when one of the advertising points is to simplify the update cycle from all the "arr"s.

yep, private for months before going public. treat this first week like a beta, those releases are fixes from launch day reports. it'll settle down, and updating is one pull

new to the public, not new code. it was private for months first. waiting is totally reasonable though

tiresome

Perhaps you will wait for the dry-aged repo.

I believe things will be from now on. People see a gap in the offerings out there and they just whip it up. There will be a certain amount of stability that the LLMs will add by default to all of them and that's it. If you are interested, go ahead and use it.

I create my own vibecoded apps for my own use, that is not the problem. releasing them for others (who might not know this hasn't been tested) is irresponsible.

it was tested though. months of my own use, vulnerability testing before release, and the readme says its new so people can decide

Reply on news.ycombinator.com