3 ms·

It is entirely misplaced based on the evidence so far. Neither of the bugs you link are currently traced back to a commit that used AI.

• Eufrat 4mo ago
  But this one can: https://github.com/RsyncProject/rsync/issues/905 https://github.com/RsyncProject/rsync/issues/905 was caused by https://github.com/RsyncProject/rsync/commit/4fa7156ccdb2ad34b034d18fe2fd6cd79adef8a1 https://github.com/RsyncProject/rsync/commit/4fa7156ccdb2ad3... and I find it pretty absurd. I don’t think AI assisted code is bad, but I really question tridge’s approach here. His post in response to to the dogpiling isn’t good (https://medium.com/@tridge60/rsync-and-outrage-d9849599e5a0 https://medium.com/@tridge60/rsync-and-outrage-d9849599e5a0). I appreciate his sense of duty to maintain rsync, but I get the very strong vibe from his response that he really doesn’t want to do this anymore and the use of AI is a way to make it easier on himself. He goes through some pretty lame arguments (aren’t humans just stochastic parrots‽ We don’t know!) and confesses he’d much rather stay retired and be sailing most of the time. I think his heart is in the right place, but this is no longer a labor of love and it shows. Also, I think another point is that, given the criticality of rsync to so many businesses maybe they could fund development and maintenance of it? What a novel idea.
  • _aavaa_ 4mo ago
    I don't find this bug absurd. It affects linux kernels <5.6 which reached EOL sometime before 2021. > the use of AI is a way to make it easier on himself. I don't see what's wrong with either this or his response in that post. > I don’t think AI assisted code is bad, but I really question tridge’s approach here. What specifically is the part you're questioning?