Please Do Not Vibe Fuck Up This Software – Rsync

freakynit

The comments are worth reading.

magarnicle

Aww, but I have such big plans for it!

rsyring

> 26k code changes in 2 months..... rsync was 67k LOC as of 236417c (latest not obviously vibecoded commit it seems?).[1] Wow. 1: https://github.com/RsyncProject/rsync/issues/929#issuecommen...

dnnddidiej

Terrible issue. If I maintained I would instaclose. Must be bad for maintainers stress levels.

krackers

Hm good timing with https://news.ycombinator.com/item?id=48334854 (OpenRsync)

theonemind

I find the way that issue was opened incredible obnoxious, but it is baffling that the maintainers seem to have let AI loose on rsync. Like, why? Why try comparatively experimental crap when your fortune and reputation is made and you're the leader of a niche and immune to market pressure and the people love the thing and it does exactly what it's supposed to and works well? It's like the Matrix, with the little rant about the primitive human minds not being able to accept paradise. You wrote the perfect tool, you won, almost undisplaceable in a niche, reliable, a metaphorical household name. It makes no sense to anyone to gamble or mess with that, it's just mind boggling. And that's still a damn obnoxious thing to do in the formal issue tracker. Bad attitude, bad faith.

impure

Oh no, not Rsync. I guess that's one good thing about MacOS shipping with an ancient version of rsync. Oh, wait, they ship openrsync now, but the command is still called rsync.

jochem9

This is the third HN post I read on this topic. Everytime the same tweet (or whatever it's called for mastodon/bluesky/etc). Did anyone actually debug the issue? Was it caused by poorly generated code, or was it caused a genuine (security) fix that accidentally caused it (potentially even in a way a human would to)?