Live data from Hacker News

Please Do Not Vibe Fuck Up This Software

github.com

211–220 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#211
post #128

Earlier quoted context omitted.

> Is there any evidence that the bug rate on rsync is any worse than it used to be? or just a screenshot from mastadon? There's plenty of evidence that rsync 3.4.3 has broken a bunch of features like incremental copies, yes. Which is why your post is a great proof of how AI derangement can make previously great engineers output broken dangerous slop.

Has rsync never broken features before, without AI?

Have features been broken in patch versions?

Re: Please Do Not Vibe Fuck Up This Software

#212
post #127

Earlier quoted context omitted.

Did he ask for help in churning all the code for no reason? Rsync was complete software. It does not need features, it needs stability and merely maintenance. If the author used AI for small, well-reviewed maintenance changes, that would be okay. But instead he is making large and sweeping changes that are entirely uncalled for and cause breakage. If the maintainer is overworked, that is even more reason not to do th…

What the hell why are you thinking you decide anything?? The man has his project and can do whatever he wants with it. Read the license.

Freedom of speech goes both ways, not just the way you like.

Re: Please Do Not Vibe Fuck Up This Software

#213
post #59

Earlier quoted context omitted.

wtf is this comment section? The author of these commits were tridge & claude. What does tridge have to do to convince the open source community that he might be a legit programmer & have a clue? Samba? Whats that? Rsync? Never heard of it. Tivo? No clue (maybe more Australian context here than others, but still). Even the comments on the github issue, are totally devoid of the context that this is a very senior open…

[flagged]

Thanks very much for this- I had not seen it.

It does not paint a pretty picture, and I did not know this context.

Perhap the tridge I knew is also of the past, but I hope not.

Re: Please Do Not Vibe Fuck Up This Software

#214
post #78

Earlier quoted context omitted.

Does an AI rewrite in Rust cancel out?

I did recently read an article about how, due to better training data, an AI writes better code in Rust than most other languages. How that translates to the number of bugs, I don't know. I would think that existing bugs would be caught, but new bugs would be introduced. The problem remains, but at least it has a new name now.

I suspect it is the feedback from the stricter compiler, not differences in training data between python and rust

Re: Please Do Not Vibe Fuck Up This Software

#216

Seem to me some people have forgotten about FOSS projects > 15. Disclaimer of Warranty. > THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FI…

Oh he's legally allowed to do this, it's just that he's a dick for doing it.

One of the issue comments says:

> Just because you are giving free soup to the homeless, doesn't mean you can piss in it.

Re: Please Do Not Vibe Fuck Up This Software

#217

Is there any evidence this was broken by AI? I feel like these day any time users find an issue in software they blame it on "vibe coding". But software had bugs before AI.

The issue is apparently this commit (someone did a git bisect): https://github.com/RsyncProject/rsync/commit/859d44fa4f14207... Which is a fix to the security issue CVE-2026-29518: https://nvd.nist.gov/vuln/detail/CVE-2026-29518 A CVE reported by VulnCheck which is a company that uses AI to find software vulnerabilitys. I would honestly blame this on bad test coverage. If you look at most of the commits where Claude…

This doesn’t even 100% mean that the code was generated using Claude, only really means the commit message was.

Write some code and then ask Claude to diff your changes and write a commit message. Now the internet hates you

Re: Please Do Not Vibe Fuck Up This Software

#218
post #142

Earlier quoted context omitted.

“No warranty” isn’t the same as “no complaints”. Otherwise there wouldn’t be an issue tracker and a discussions section. The issue in question has already gone to crap and your point has been made there as well. It could definitely have been handled better, by all parties involved, but blindly quoting legalese isn’t going to resolve anything or make it better.

An Issue tracker is to track issues regarding the behaviour of the program, not the behaviour of the maintainer.

Disagree. Issue trackers are used for all sorts of things in all kinds of projects. Go look around, plenty of examples out there. Unless the maintainers have explicitly specified how issue trackers are supposed to be used, (reasonable) discussions are usually allowed on issue trackers, especially GitHub Issues.

Re: Please Do Not Vibe Fuck Up This Software

#220

Nobody whose software you use for free owes you anything. It is so important not to lose sight of this. If you feel like they do owe you something, that's only because years of habit -- years of using other people's software for free, and having the good fortune of finding it generally to improve in quality over time -- has caused your baseline to drift from the true state of affairs, which is that nobody whose softw…

Indeed you can step down, but as one of the comments says:

> Just because you're giving free soup to the homeless doesn't mean you can piss in it

Post reply on HN