Tridge has responded on the rsync vibe disaster

https://medium.com/@tridge60/rsync-and-outrage-d9849599e5a0

* you're all dumb haters
* AI is a revolution just in the past few months
* yes there were regressions but,
* the new test suite is awesome you haters
* openrsync doesn't pass the new test suite! ha, you fools! well that's cos it targets an older version but,

at least it reads like he wrote it by hand

i can pick the particular mastodon posts he's reacting to here

rsync and outrage

I gave up blogging a long time ago (apart from an occasional thing about ArduPilot), I tend to just write code and hope people find it…

Medium

@davidgerard It seems to me that this highlights that the real problem isn't a code quality problem, it's a project management problem: he's old and would rather sail his boat and he's trying to maintain rsync on his own and (TLDR: don't wanna, let's just AI it instead).

It's this XKCD strip in a nutshell: https://xkcd.com/2347/

@cstross @davidgerard I don't think handing stuff over to LLMs is solving any issues, though. He could just hand over maintainership, or formally archive rsync and let others fork it while he's off, sailing. The end result would've been the same (people switching to forks) but without any of this drama. It's not like there isn't precedent for this, either: Dylan Araps just archived all his repos before going off farming and making wine, and people forked the repos they cared about. And unlike the current rsync fiasco, nobody was upset at Araps because he had every right to just walk away and let others pick up the work they deemed worthwhile.
@reiddragon @davidgerard @cstross I think the problem is that he doesn't want to lose ownership of the project; he wants to "leave a mark," let his name be known by maintaining something this big.
@wildfire @davidgerard @cstross he already left his mark by (co)authoring it. All he's doing now is tarnishing his own reputation.