263
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 03 Jun 2026
263 points (96.8% liked)
Programming
27173 readers
387 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Well rsync is a pretty integral utility for a whole array of software at this point, and I guarantee you that not all of its userbase has the expertise required for direct contributions. I don't think it's fair to write off the complaints of people like that as irrelevant, especially if they have a stake in rsync working well for them without having to worry about AI hallucinations screwing them over.
Well yes but.
This guy is already retired, he wants to spend his days sailing and here we are bitching about rsync not being good enough while we all use if for free
Most of us won't be able to help code
But most of us could help with translations
Many of us could help with documentation
Some of us could contribute regularly nwith small financial donations
Some of us might have enough knowledge and expertise and experience to help code
The point is: rsync need more resources. Either we get him more resources or we STFU about the retired dev using AI. We can't have it both ways
Then retire. All the time people think it's maintained it feels safe to not get involved.
I agree. Either retire and pass the torch or stop using "im retired" as an excuse. You can't have both
I agree with the worry and wanting an alternative but demanding what the dev does is where it crosses a line I feel
I agree with that too, though I think the self-righteous attitude like that of the person I'm replying to swings in the opposite direction a little too hard for my liking. There's a happy balance, y'know?
People shouldn't complain in a dev's ear like they owe them something they never promised, and people trying to call that out shouldn't counter it with a demeaningly confrontational demeanour. Obviously that's a lot to ask for on the internet, but it's a good thing to try for at least.
Tell me about it, I am skeptical about AI and I kinda wanna know the True Positive, true negative, false positive, false negatives with these AI classified bugs. Still a useful tool.
I just think it's unreasonable to ask someone to do dev work for free, either pay or contribute (code, docs, help in misc ways) or cash (and pull out when they do something you don't approve that's your right). But until there's real fuckery let's just open bug reports and complain about real issues that can be fixed.
It's provided as is, no warranty, no guarantee. If you built your life around it, that's on you, not the dev. If you want something else, do it yourself or pay somebody to do it for you.
Fair, but a little empathy for rsync users who only mean well would go a long way. The everyone-for-themselves mentality doesn't tend to be very helpful most of the time, if ever.
Meaning well and blasting the rsync maintainer with absolutist anti-LLM messages are very different things.
Th rsync maintainer is ironing out issues. Use an old version and let him cook. Once things are stable, then pull the new version. If you're on arch or another unstable distro that always pulls the latest version, this is what you signed up for. Staying on the bleeding edge means you'll bleed.
It doesn't excuse attacking he maintainer who seems to be making a genuine effort. That shows a lack of empathy.
…Which is why I specified those who only mean well. Obviously that doesn’t include the less pleasant crowd.
We're mixing up two things here. There's valid criticism. And there's the people who want to unleash some social-media style shitstorm. The latter show up in large groups and add some unsubstantiated comments, lots of emojis and drown any kind of conversation. But that doesn't really take away from the valid criticism. For example a maintainer shouldn't tag a version and release it, when it's not ready to be released. That's the 101 of software development. You can expect as much. Because the "bleeding" thing isn't really how it works. Once there's a new minor release tagged by the devs, it's supposed to be picked up by the distro maintainers and get into any distro's repositories. Doesn't matter if it's Arch unstable or Debian stable. They don't want bugs and security vulnerabilities in their distro, either. Especially not when it's 6(!) CVEs! And the Debian dev's in fact reacted to this. And they even backported stuff to oldstable so the people who run the rock-stable stuff from 3 years ago get the patches! So it really doesn't matter... Run a bleeding edge distro, or a stable one and don't update it for 2 years, you'll be affected by this both ways.