It's rather ironic that in profit making enterprises using AI are not only encouraged but also part of KPIs. But in open source it's scourge
Rsync 3.4.3 has hundreds of Claude commits
51–60 of 86 posts
Re: Rsync 3.4.3 has hundreds of Claude commits
#52What's the difference between experience a human made bug versus an AI made bug in software?
A human preserves more context and might remember what they did and when pointing out a new bug, they often have an idea what's wrong.
I cringe any time I read loaded questions like GP's. Have they ever met a human in their life?
Re: Rsync 3.4.3 has hundreds of Claude commits
#53I saw an exceptionally long and thoughtful post on Mastodon from "Space Hobo" https://teh.entar.net/@spacehobo that definitely deserves reprinting here ----- I actually worked at the same place as Andrew Tridgell, over a quarter-century ago. I got to know a few of the OzLabs folks during their immediate post-IBM years, and always had the highest respect for them in that way where you feel acute impostor syndrome when…
> If TRIDGE of all people can't handle #LLMs without a slopocalypse, no one can. > That means you. That means someone you admire who is intelligent and careful and considerate. Not even someone whose opinions on technology you respect a great deal. I disagree. The amount of commits is not from somebody who is carefully reviewing the new code and considering the changes done. It's from somebody who thinks they are in…
Humans are lazy, and the mistakes of being lazy when vibe coding are orders of magnitude larger than being lazy when you have to do the damn thing yourself. In fact in the latter case, laziness is a feature.
If the AI-powered software world depends on humans not being lazy, we're all fucked.
Re: Rsync 3.4.3 has hundreds of Claude commits
#54Maybe time to pursue alternative implementations[1]. [1]: https://michael.stapelberg.ch/posts/2026-05-24-minimal-memor...
Re: Rsync 3.4.3 has hundreds of Claude commits
#55This is a problem of insufficient checking happening in-between a PR being made, and it being committed. Imagine you have a low quality coder in your coders, they produce a lot of code, but while some of it is fine, some of it is... dubious. That is no different from an AI and the way you deal with it is the same. You check the PR before committing it. To allow PRs from them (or anyone really) to get merged without p…
The commits were all from the original inventor of rsync. Not a low quality newbie coder.
I stand by my post.
Re: Rsync 3.4.3 has hundreds of Claude commits
#56Earlier quoted context omitted.
The commits were all from the original inventor of rsync. Not a low quality newbie coder.
"To allow PRs from them (or anyone really) to get merged without proper checking for bugs etc is just sloppy repo management." I stand by my post.
The commits in question are no pull requests.
Re: Rsync 3.4.3 has hundreds of Claude commits
#57Earlier quoted context omitted.
I don't think using AI as such is the core problem here. It's the type of use. Vibe coding, brain off coding and blind trust are the issue, and an issue everywhere, just enterprises were never really about quality in the first place. But eventually, they too will generate more crap than they can handle.
I mean, we have no idea how tridge is using claude. I would easily give him the benefit of the doubt that he's not vibe-coding, is involved in the change (not just turning on auto-accept), and reviews the output before committing. But it seems like everyone's immediate hot take here and on Mastodon is to assume the worst and shit on him.
For rsync in general, I would say that the important value is the trust in it not breaking my data, more so than other projects. That trust can be broken in different ways, AI or not, and the means are of a secondary concern. I hope this gets sorted out soon.
Re: Rsync 3.4.3 has hundreds of Claude commits
#58I reckon we will soon see a growing movement of maintainers forking popular open-source projects to the point before vibecoding was introduced to the development process. I can definitely see myself supporting this. Vibecoding promotes the uncontrollable growth of features, and thus bugs, when the vast majority of software benefits from stability. It should be possible to be done with development, barring security pa…