rsync was basically done until the maintainer discovered vibecoding
-
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
-
rsync was basically done until the maintainer discovered vibecoding
@hailey I hope Unison gets a unidirectional mode & also a package for Termux & Chimera Linux. I would probably do it myself if I knew how to package software.
-
rsync was basically done until the maintainer discovered vibecoding
@hailey Oh FFS. Pinning time.
-
rsync was basically done until the maintainer discovered vibecoding
@hailey@hails.org it hurts in places I cannot soothe
-
rsync was basically done until the maintainer discovered vibecoding
@hailey oh god
-
-
rsync was basically done until the maintainer discovered vibecoding
@hailey Yikes!
-
rsync was basically done until the maintainer discovered vibecoding
@hailey we had things that worked as intended. Now we have AI and start reinventing the wheel.
-
rsync was basically done until the maintainer discovered vibecoding
@hailey noooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo
-
@hailey Gonna lock the version on all my systems (altough Debian, Void and FreeBSD might do that too and I don't even have to)
@speaktrap @hailey What is the last slop-free version?
-
Given a choice between freezing all packages before vibe coding was "discovered" and packaging upstream releases, the former is not fully practical. The Gentoo social contract requires following council mandated policies about how one interacts with the Gentoo project, but doesn't control what other projects merge.
The kernel is slopcoded too, but we can't exactly do without that, now can we? Well, okay, we recently added experimental GNU Hurd support.
-
Given a choice between freezing all packages before vibe coding was "discovered" and packaging upstream releases, the former is not fully practical. The Gentoo social contract requires following council mandated policies about how one interacts with the Gentoo project, but doesn't control what other projects merge.
The kernel is slopcoded too, but we can't exactly do without that, now can we? Well, okay, we recently added experimental GNU Hurd support.
That doesn't mean we have to put up with horrid slop, it just means that blanket forbidding all LLM assisted software is in practice unenforceable outside our community (where we cannot analyze PRs and require assertion of non-use).
Inevitably the result of slop is that the software deteriorates and doesn't work, and Gentoo may respond by freezing updates or removing it entirely (see chardet being frozen).
We do what we can, and we make our disapproval clear regarding the rest.
-
That doesn't mean we have to put up with horrid slop, it just means that blanket forbidding all LLM assisted software is in practice unenforceable outside our community (where we cannot analyze PRs and require assertion of non-use).
Inevitably the result of slop is that the software deteriorates and doesn't work, and Gentoo may respond by freezing updates or removing it entirely (see chardet being frozen).
We do what we can, and we make our disapproval clear regarding the rest.
-
The fact that Gentoo, unusually among distros, actually supports (unlimited) multiple versions of a package and for users to pick and choose their versions, means there is a *lot* of latitude for isolating the dangers of slopcoding destroying a package. It's generally always possible to discover that the project fell apart and stopped working, and just tell portage to reinstall the old version. Removing slopcoded trash from the distro is "simply" a matter of removing one choice.
-
rsync was basically done until the maintainer discovered vibecoding
@hailey shit. Pinning now
️
There goes my backup! -
rsync was basically done until the maintainer discovered vibecoding
Wasn’t it the “complete software”?
-
R relay@relay.publicsquare.global shared this topic
