rsync was basically done until the maintainer discovered vibecoding
-
rsync was basically done until the maintainer discovered vibecoding
@hailey Distro packaging systems need a workflow that auto pins all packages at last tag before any commits crediting slop bots.
-
rsync was basically done until the maintainer discovered vibecoding
@hailey Apparently some people can't comprehend that software can be completed and finished
-
-
@EndlessMason @WTL @hailey when I was a kid in Alberta we’d visit a cave some summers and go into the dark of the mountain. Sometimes I think that might be the best place. https://hikebiketravel.com/canyon-creek-ice-cave/
-
@odd@mstdn.social @hailey@hails.org It generally doesn't prevent AI generated projects from getting packaged, but considering that this is a core package for Gentoo, it likely will have additional review and such done, which will affect if it gets unmasked and such?
-
@EndlessMason @WTL @hailey when I was a kid in Alberta we’d visit a cave some summers and go into the dark of the mountain. Sometimes I think that might be the best place. https://hikebiketravel.com/canyon-creek-ice-cave/
-
rsync was basically done until the maintainer discovered vibecoding
@hailey damnit, that's my backup program, picked because its easy & doesn't have unwieldy imports to restore
-
rsync was basically done until the maintainer discovered vibecoding
@hailey Oh hell, no one should be allowed to fuck up rsync like that. Package pinning time!
-
rsync was basically done until the maintainer discovered vibecoding
@hailey@hails.org It's so incomprehensible. For someone to develop rsync, a software that serves a particularly sensitive purpose and thus must be a rock-solid block of bits, I would assume:
-
The maintainer actually used and depended on rsync, and would be the first to suffer if the software's dependability started to degrade;
-
That the maintainer actually took pride on rsync being so well-reputed and considered an integral part of many, many people's workflows;
-
More importantly: if the maintainer felt unable / simply didn't want to continue working on rsync for any reason, that he would try to pass the torch to someone that ensured its future in the same molds.
Instead, rsync is proudly making an effort to join the rapidly-growing lists of software that will be remembered sadly for quite some time for their pre-LLM existence. Until one day they're simply forgotten.
-
-
@hailey FFS can we fork rsync and have a non-AI coded version?!
Why don't intelligent people get this: AI (LLM) coding takes vast amounts of power and resources and puts control in the hands of totally unethical mega-corps and billionaires. Not too mention the copyright infringement and lack of attribution that comes with LLM-coded slop.
@fionasboots @hailey Already done a few years go due to some licencing issues to produce openrsync (https://github.com/kristapsdz/openrsync)
-
rsync was basically done until the maintainer discovered vibecoding
@hailey "AI makes you 10x more productive"
-
rsync was basically done until the maintainer discovered vibecoding
@hailey oh hell no
-
rsync was basically done until the maintainer discovered vibecoding
I looked through the history and a lot of this would be unnecessary if rsync didn't include a daemon. I, for one, have no use for it, and it seems to me like it would be a good idea to architecturally separate the one-shot CLI tool from the persistent service.
-
@fionasboots @hailey Already done a few years go due to some licencing issues to produce openrsync (https://github.com/kristapsdz/openrsync)
+1 informative
-
-
rsync was basically done until the maintainer discovered vibecoding
@hailey oh no. Oh no oh no oh no oh no
-
rsync was basically done until the maintainer discovered vibecoding
@hailey wait, is rsync slop now? -
@glitchcake @hailey who doesn't ?
-
@hailey wait, is rsync slop now?
@LunaDragofelis @hailey apparently so
