Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Please Do Not Vibe Fuck Up This Software

github.com

Post reply on HN
Print view View original

221–230 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#221

Post by fg137 »

abc123abc123 wrote: post #172

Jesus Christ... this anti-AI thing is getting ridiculous. If the code is good, bug free, and easily understood, who the f*ck cares? If a maintainer just accepts any code, without review or control, humans, just as well as "AI:s" can submit crappy code. I can only conclude that this is some kind of misplaced frustration due to job protection and feelings of insecurity that makes people this polarized and religious.

Sounds like you could have benefitted from reading the article first, as your comment is completely the opposite of what's happening here.

Re: Please Do Not Vibe Fuck Up This Software

#222

Post by lioeters »

basilikum wrote: post #206

This is anti-AI slop. Posting a screenshot of someone else's text as an issue is about as low effort as it gets. It's also just a completely random accusation. I experienced a bug; the software contains some amount of AI code; that must be the reason. Because there is no other way bugs are ever made. Bugs only came to life in 2023 with ChatGPT. No need to look at the actual code, see if the bug is in an AI generated…

> low quality AI slop that causes bugs

That's exactly what's happening here. The tone of the issue was immature, but there is a legitimate problem that cannot be brushed away as "anti-AI". The real issue is the irresponsible use of buggy machine-generated code in a project that many people depend on. Users are pissed and rightly so.

Re: Please Do Not Vibe Fuck Up This Software

#223

Post by [deleted] »

reliablereason wrote: post #123
eloisant wrote: post #96

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…

[deleted]

Re: Please Do Not Vibe Fuck Up This Software

#224

Post by layer8 »

KolmogorovComp wrote: post #162
latexr wrote: 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.

If issues with the program are caused by behavior of the maintainer, it doesn’t seem inappropriate.

Re: Please Do Not Vibe Fuck Up This Software

#226

Post by [deleted] »

throwaway7356 wrote: post #149
consp wrote: post #125

Earlier quoted context omitted.

> I think this behavior is very silly and people are just trying to justify their hate to AI by latching onto every possible thing It's not silly to have issues with something. People act on their issues. Possibly not the issue underlying the commit at hand here but something else, and act on it which makes it something to consider. My guess is people are tired of the "AI is the greatest thing since [cultural referen…

> and grasp at every straw to combat it, which is a sane response Attacking every open source maintainer who might use AI for the sin of having used AI because one hates AI is just abusive behavior, not "sane response". What would the "sane response" be for people tired of the "AI is being forced down my throat and I need to combat it by attacking open source maintainers" side? Grasp at every straw to combat such beh…

[deleted]

Re: Please Do Not Vibe Fuck Up This Software

#227

Post by zbentley »

Did anyone in that issue thread ever … describe an issue? As in steps-to-reproduce, expected vs. observed behavior, all that?

Like, this was posted on an issue tracker. “Your commit messages reference Claude and some guy on bluesky thinks some unspecified issue he had is related to those commits” is not an actionable issue. All the rest of the discussion aside, if this were my project I would close and lock with “not enough info to reproduce”. There are better places for general discussion about AI and forking and emitting rage.

Re: Please Do Not Vibe Fuck Up This Software

#228

Post by [deleted] »

tardedmeme wrote: post #220
akoboldfrying wrote: post #72

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

[deleted]

Re: Please Do Not Vibe Fuck Up This Software

#229

Post by layer8 »

scared_together wrote: post #6
rsyring wrote: post #4

> 26k code changes in 2 months..... rsync was 67k LOC as of 236417c (latest not obviously vibecoded commit it seems?).[1] Wow. 1: https://github.com/RsyncProject/rsync/issues/929#issuecommen...

When I look at the commits themselves, most of the ones generated by Claude are testsuite changes, or at least labelled as such. https://github.com/RsyncProject/rsync/commits/master/

The correctness of tests is as important as the correctness of the main code. Changing test code isn’t somehow less critical than changing the main code.

Re: Please Do Not Vibe Fuck Up This Software

#230

Post by [deleted] »

tardedmeme wrote: post #216
KolmogorovComp wrote: post #130

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.

[deleted]
Post reply on HN