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

161–170 of 534 posts

Re: Please Do Not Vibe Fuck Up This Software

#161

Post by rf15 »

dannersy wrote: post #60
theonemind wrote: post #14

I find the way that issue was opened incredible obnoxious, but it is baffling that the maintainers seem to have let AI loose on rsync. Like, why? Why try comparatively experimental crap when your fortune and reputation is made and you're the leader of a niche and immune to market pressure and the people love the thing and it does exactly what it's supposed to and works well? It's like the Matrix, with the little rant…

A couple years back, I think I would have bent over backwards to defend the maintainers. It is a gruelling and thankless effort to maintain any open source project, let alone one as established as rsync. I guess I just don't see AI being a net positive anywhere, and I have to see this backlash to using gen AI as a good course correction from the general populous. There are other posts talking about the instant gratif…

> instant gratification

I'm with you. I don't understand why it affects some people more than others. To me, using AI triggered my sense for drugs and addiction after a while: when your first association for an engineering product is "it feels _great_!" then run, it's just cocaine with extra components.

A tool should not make you feel good, just accomplish the task.

Re: Please Do Not Vibe Fuck Up This Software

#162

Post by KolmogorovComp »

latexr wrote: post #142
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…

“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.

Re: Please Do Not Vibe Fuck Up This Software

#163

Post by weiliddat »

rf15 wrote: post #158
weiliddat wrote: post #137

Earlier quoted context omitted.

Maybe I'm getting too skeptical. I have a feeling increasingly many of the comments on HN and the GitHub issue are just bots ragebaiting other people (incl. the maintainer)...

[flagged]

I'm not sure how to interpret your comment. It could be

- a response to my comment saying that I am "illiterate" and cannot differentiate LLM output vs actual human comments (in that case I'm not sure what you're adding to the discussion here beyond a personal attack)

- a general comment saying it's getting harder for people in a position similar to us (i.e. tech / tech-adjacent who interact a lot with others who write with LLM assistance or via LLMs) to differentiate human/AI output.

I'll assume good faith and you mean the second. In that case maybe you can explain the "fundamental problem" you're referring to?

Re: Please Do Not Vibe Fuck Up This Software

#164

Post by androolloyd »

izacus wrote: post #126
mattbee wrote: post #82

Earlier quoted context omitted.

But there's been security fixes in most releases of rsync! Even then, why would a security fix be some kind of strike against AI? We've all seen LLMs being used to tease out the most serious and obscure bugs in C codebases. I'd expect to see a lot of security fixes for an ancient, well-used codebase when an LLM analyses it. Where is the slop commit here? And why is that commit evidence that tridge has lost his mind t…

The part you're missing is that those "fixes" broke a lot of existing functionality.

Bugs are bugs and need fixing. How dense can people get.

Re: Please Do Not Vibe Fuck Up This Software

#165

Post by xnx »

otabdeveloper4 wrote: post #133
koehler wrote: post #36

I truly don't get it You have a rock solid piece of software used by an infinite amount of people and other services. It works fine, does it's job and just have some time to time updates due to minor bug fixes. Why do we need AI here? And more over, why people is saying "fork it and use the previous version". It should be actually all the way around, create a parallel fork younamethetool-ai and keep the OG untouched.…

> Why do we need AI here? AI psychosis is a real thing and an actual mental health issue.

Similar to anti-AI derangement

Re: Please Do Not Vibe Fuck Up This Software

#166

Post by fzeroracer »

helsinkiandrew wrote: post #160
koehler wrote: post #36

I truly don't get it You have a rock solid piece of software used by an infinite amount of people and other services. It works fine, does it's job and just have some time to time updates due to minor bug fixes. Why do we need AI here? And more over, why people is saying "fork it and use the previous version". It should be actually all the way around, create a parallel fork younamethetool-ai and keep the OG untouched.…

> Why do we need AI here? As several comments in the issue mention, it's up to the developers that contribute to an open source package to decide how they do it. Complaining on an issue tracker (apparently without proof) about AI ruining a piece of software is a form of "Open Source contributor abuse" discussed frequently on Hacker News [1] https://github.com/RsyncProject/rsync/issues/929#issuecommen... > The issue t…

[flagged]

Re: Please Do Not Vibe Fuck Up This Software

#167

Post by mort96 »

KolmogorovComp wrote: post #134
mort96 wrote: post #95

Earlier quoted context omitted.

No: https://github.com/RsyncProject/rsync/commits/master/

Almost all the commits are regarding the testsuite or CI, both of which are IMO great use of AI.

I think that’s misleading. Yes, almost all commits co-authored by Claude lately are about test suite and CI, but that’s just because almost all commits lately are about test suite and CI. The commits which aren’t test suite and CI are also co-authored by Claude. Go a bit further back in the commit history (April 29 onwards) you still see a sea of non-CI/testsuite Claude commits.

Re: Please Do Not Vibe Fuck Up This Software

#168

Post by Npovview »

seba_dos1 wrote: post #29
bulbar wrote: post #25

Earlier quoted context omitted.

To me it seems people had actual problems with newer versions. Additionally, a significant portion of the code changed within a very short time frame. Doesn't matter if they did it by hand or with AI.

I just had the first case of a file not being copied correctly after using rsync that I noticed a few days ago. It was a raw image file so it was visually noticeable, some lines of pixels just went black. It may be unrelated, it may not have even been rsync's fault, but this drama and timing just makes me wonder if I got clauded there.

Do you not do the md5 or sha hashes of the copied zip file?

Re: Please Do Not Vibe Fuck Up This Software

#169

Post by watwut »

oytis wrote: post #84
Quarrel wrote: 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…

I'm not sure about tridge personally, but I've regularly seen real competent engineers introduce obvious hallucinations when using coding agents. Review fatigue is real, and you just cannot own the code you didn't write to the same degree as the one you wrote

My consistent observation is that seniors who do only or mostly code reviews for several months end up making worst and worst code review. They nitpick thinks that dont matter more and more ... and miss big architectural issues, maintennability issues and bugs more amd more.

There is no reason to think reviewing AI code more then writing own wont have the same effect.

Re: Please Do Not Vibe Fuck Up This Software

#170

Post by bakugo »

antirez wrote: post #120

A few years ago, the probability of such shit reaching the Hacker News home page was near zero, because regardless of the merits, here was not full of normies that could not understand when a behavior is unacceptable (I'm referring to the violence of the language of the issue). And now, here we are, surrounded by people that can't tell the most obvious things.

Similarly, a few years ago, I would've never expected "my magic code generation machine is doing all my work for me now, I don't even bother looking at what it does anymore!" to reach the Hacker News home page on a regular basis, either, yet here we are.

Irrational actions lead to irrational reactions.

Post reply on HN