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 behavior?
That's not what happened, and I think you know it. The number of LOC introduced in the last 2 versions of rsync is off the charts. And there are bugs. I've been in a situation like the author of that issue. Upgrade a package and things fall apart and it would be very, very expensive to debug it to file the appropriate bug reports... so I roll back to a known good version.
Yes, the language the person used wasn't the greatest.
IMO, this is a litmus test for how you feel about AI. For the people that hate it, it's just a big pile on and "I told you so" ... we don't have enough info about the author to know if they are anti-AI. We know they are against using AI in a BAD WAY.
The regressions are the issue. If the software was working as expected, no one would be coming after them for “the sin of using AI”.
I don't understand what novel problem you think you've uncovered here.
But there is good news, at least I think. AI is also moving processes ideas and safety guards along at a faster rate. The only real downside is right now, at least, the amount of code being created outside of our safeguards has accelerated much much faster. This has happened in the past with software, so I am not too worried.
I absolutely understand and agree. As I said, I understand the underlying reason.
The silly part is the brigading - issues should be adressed on their own merits. The specific GH issue, and some of the comments therein, make the whole crowd they're affiliated with look bad. (imho)
drive-by 20-file pull-requests that ultimately end up costing maintainer's burden seems to hit hard here.
Note this is not what OP called silly. It's possible to take legitimate issue with something, then act silly about it. People are free to their opinions but not necessarily to (as an extreme example) write their opinions on the wall with their excrement. Regardless of any veracity behind the opinion, some decorum is expected in its expression. (I guess unless one is explicitly doing away with decorum but that's when violence takes its place.)
You can grep commit logs by “Assisted-By” these days and there sure is a whole bunch of LLMs.
Let's engage in some parallelism then
This happens with literally everything in our society. Right now, every single food product seems to be infused with protein. In the past, they've had GMOs removed, MSG removed, been Fiber-infused... the list goes on and on.
We don't see people bullying and threatening grocery store clerks and managers over clear hype-cycle bullshit. Why? Because every rational person knows this is pure nonsense.
This behavior is NOT sane.
As many others have pointed out, this is just a regression that occurred during regular software development. There's nothing remarkable here that makes it AI-specific, other than that the contributions were AI-assisted. Regressions in software happen. You roll back to a stable version and make a bug report. You don't shit your diaper and sling it at the maintainer.
Acting like a giant fucking douche is NOT NORMAL BEHAVIOR.
Yes, but some should absolutely be caught with a robust test suite, especially if it is not an edge case.
When was the last time there was a breaking regression in SQLite again?
A mistake was made. There are well worn paths for fixing the mistake. Acting like a giant fucking petulant pissbaby is not the critical path to getting things fixed and is deeply corrosive to the positive collaborative environment we’ve all spent decades building within shared, community software.
Get the fuck over yourself.
Yeah for human, by humans
For some critical software, open-source or not, a regression could literally kills, that's why I put SQLite as an example. A simple miss should NOT pass into stable, if it's an edge case due then yeah learn from it and built a test suite for that if possible
rsync is highly popular tools and a lot of people depends on them, whether you like it or not. At a certain point (I don't know what point, 10k, 20k, 500k users?) maintainers should respect the user expectations over their own ego and convenience
This is a problem for OSS in general, people treats their project like a hobby because it didn't pay enough, or corporates uses it without contributing back
From a cursory look, it looks like a security fix in response to a CVE surfaced a coding error which (as far as i bothered to check) has been present in the code since 2007.
This is so banal that it's actually hilarious to see people lose their shit over it. But of course nobody is talking about the actual issue but about the _hypothetical potential for issue_ introduced by potential use of AI. It's so meta i don't even know how to make sense of it.
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 reference]" being forced down their throat and grasp at every straw to combat it, which is a sane response in my opinion and should be taken into account.