Untrusem <[email protected]> writes: > So I saw there So I saw there was a update for waybar in guix repo > and then I checked the release notes and saw that it was using > co-pilot and claude both and I personally don't like to use software > that have LLMs if I can avoid that. > > I would have not known that waybar author started using LLM or not if > I didn't visited the repo myself. > > So that's why I wanted a way to know when a guix package updates or > gets added. It should explicitly mention that LLMs is being used in > the software to let the users know that the software they are using is > slop or not.
I also get a feeling of walls closing in, and i'm unsure what the best way forward would be here. The tough stance[0] of the (amazing) Zig project is one of the things keeping me sane. Personally, i'm considering setting up a minimal setup with slop-free components. In practice this would probably mean NetBSD, busybox, wayland. Forking and maintanining pre-slop versions of parts. My prediction is that there will be a continous cycle of people spending their time and love writing good software, and having others come in and use their gigawatts to extend it into whatever direction, brag about it online[2], and go on to abandon it for the next run-by. We probybly need to form new communities based on a rejection of synthetic software, i would love to have forums where i don't have to scrutinize every new interesting project for AGENTS.md's full of nightmare fuel and 17k lines initial commits. I'm seriously not sure if the traditional Copyleft is up to the task here, and we might have to rely more on abstention and community building based around this very abstention. A software veganism of sorts? (the parallel applies in more than one way, refusing resource hungry processes in favor of lower energy ones) Anyway, that's my rant. I'm desperate for something like this to take real form. Happy hacking y'all and let's try to keep our software organic! [0] https://ziglang.org/code-of-conduct/ [1] https://www.netbsd.org/developers/commit-guidelines.html [2] https://blog.meshcore.io/2026/04/23/the-split
