I looked at the rsync commit log and basically every commit since March says "tridge and claude committed." Andrew Tridgell, the guy who literally invented rsync in 1996. Now hes using a chatbot to write the code and proudly displaying its name right there in the commit.
And before anyone goes "calm down its just a typo fix" no. The recent stuff is the security fixes for 3.4.3. The symlink race CVEs.. You know, the exact part where you want an actual human who understands what hes doing, not a machine that spits out code that looks correct but has correctness errors.
Do you get how insane this is? Rsync is the thing holding up basically every backup system on earth. Your NAS uses it. Distro mirrors use it. The server with you grandmas photos uses it. And now the plan is to let a token predictor that can't even count the amount of letter R's in "strawberry" write code for it.
"But the tests pass." The tests pass because the AI probably wrote the tests too you walnut. Its a loop of confident nonsense thats grading its own homework, and the first time it hits an edge case nobody fed it its gonna silently corrupt something and noone notices till the backups are already poisoned.
I'm pinning v3.4.1 and not updating again. If you defend this, dont say nobody warned you when the data loss posts start appearing.
Did they really need AI to set a number to 45?!? Also you can do this centrally in the repo settings and don't need to do it on every single workflow!
Conclusion: Garbage code
lol - I don't use any AI code in projects I'm paid for at all, but I experiment in my free time. One of the few advantages is that I can keep going when I'm completely braindead, like before first coffee or when I should have gone to bed 3 hours ago. So I prompt things like "run those test thingies" when I can't even remember the gradle/maven task that I use 50 times per week.
So yes, for me, strangely relatable :-)
This is what AI does...it "removes the friction" of doing large scale find and replace operations consistently so your whole repository becomes terrible, repetitive patterns because it made it much easier to do the wrong thing.
My question is if that number is set/used separately in all those places why isn't it defined somewhere more centrally. It's silly that you need to update so many files for such a simple change.
I once worked with a dude that basically maintained what would've been a database in a reasonable code base through a series of data structures hard-coded into the Java code. When there were changes, he would roll through the dozens of files and add additional records into the code. AI has probably made his "job" a snap...if he still has one.