He is not giving anyone piss soup. He’s leaving it on the sidewalk, you take it on your own knowing what it is.
This. It’s literally someone putting food in a container and saying: it’s here in case someone needs it.
You don’t want/need it? Don’t take it. Open source. No force feeding, just
git push --force
Being on Debian with just security updates and AppImages is the smartest thing I’ve done. Hopefully, non-AI forks are mature by the time the new Debian version is out
So the devs are now split in two camps, one that “use whatever means for your goal” and one is “fuck AI and everyone who thinks its a great thing”
I am torn
ITT entitled people, who would never pay a single cent for rsync nor ever contribute to it, having a big mouth about it.
Also the analogy is crap. It’s free soup on somebody’s compound that anybody can walk in and take at their own accord. People walk in, take it, build a business or dependency around it, and get pissy when the recipe changes. They don’t want to take the recipe and fix it themselves, instead they demand the cook change it for them. “My customers are unhappy with the soup you make in your backyard”. The cook is well in his right to tell them to fuck off.
Agree. It seems a lot of people love open source software only because it’s free…
Note I’m not including hard core open source zealots who support the developers.
Serfs needs to subordinate to the masters.
“Pissing in the soup” doesn’t really work here unless you’re adulterating the software with something malicious.
Unfiltered river water might be a better comparison. It’s not intentionally poisoned, but you might not want to drink it if you don’t have to.
This was in response to rsync having horrible new bugs from vibe coding that were so bad that people thought they had malware. Does the intent matter when the end result is the same?
Holy crap I thought rsync is a super serious and professional program. Didn’t thought they ruin it with vibecodeing.
A lot of important infra depends rsync.
Apparently the project got overwhelmed with LLM vulnerability reports, so the last person in the world who actually cared enough to keep maintaining it gave up and gave in to the spop himself.
I read that the guy is a legend and genius (I believe that because rsync is fantastic. He invented that). I trust in him knowing what he’s doing. We should give him a hand if we want it to be better.
I believe serious one is openrsync, the openbsd fork that does NOT have vibe-coding.
You mean like near every program?
Tell you what that Rsync thread is just a goldmine.
While I’m generally not one to complain about something I’m getting for free, and I do understand the dev wanting to make more efficient use of their time…
I don’t think people are wrong here expressing their annoyance at what was previously feature complete and stable software being vibe-code updated into a buggy mess.
… And that’s without mentioning the ethical and security issues posed by vibe-coded software.
I think we need to support the dev so they don’t need to use vibe coding. From all I see he’s overwhelmed and he doesn’t even get paid for this.
If you don’t like it, fuck it or fork off
But if the chef wants oranges in the pea soup, and you don’t like that, it’s fair to say go to another soup kitchen.
Except that his idea of oranges is piss.
If it’s about AI slop pull requests, it’s more akin to a microwaved orange tbf.
Mmm warm orange juice and toothpaste!
And when everyone starts to avoid that soup kitchen, it makes the chef a dick
Depends if you are upfront about it or not
Funny, that nearly tracks for the US, except it’d need to feed said homeless first. So far, it’s just pissing on us poors. No soup.
Obligatory “No soup for you!”
I’d give up soup if the piss’d stop raining, flooding, rotting everything we’re each trying to work on. ✊🏼
The gilded shower.
I suspect this might be from the jqwik thing going on right now. The maintainer of that library added some anti-AI “fuck you” code to delete vibe coders’ “work”
This is rsync. The “piss” refers to AI code contributions.
Could also be rsync, recent vibe coding changes there broke things and maintainer is also getting pretty annoyed with the comments.
They didn’t add any code to jqwik. It was just an instruction. A string.
Does that really make a difference?
yes. normal usage works as expected
Yes? If it had been in the readme it would have worked the exact same way. It’s not code, they aren’t pissing in anything. Literally no one but an AI would have a problem with it.
This is from rsync repo.
…Regardless of the code assistant, I’m not seeing any cause for alarm in my personal usage, yet. Feature requests and issues are getting closed, even urgent security ones that shouldn’t have been posted in that manner:
https://github.com/RsyncProject/rsync/issues/871
https://github.com/RsyncProject/rsync/issues/882
Seems like business as usual:
https://social.treehouse.systems/@thesamesam/116662824873341085
One thing I will say on rsync is that regressions aren’t new with it. It does something hard: it has to deal with symlinks. Releases have often had regressions for a long time, especially for security fixes, and it long predates LLMs, because symlinks are hard. Of course seeing a gazillion Claude commits still makes me uncomfortable, but it’s important to see what’s new as well.
Unsure if they’re talking about rsync introducing AI code and breaking. Or that dev that introduced code that broke systems using AI.
deleted by creator
