Ludovic Courtès <[email protected]> writes: > Sorry I didn’t mean to bring the discussion in that direction. My > question is more what to do first about packages with vibe-coded > software, and then more generally to avoid indefinite growth—but the > latter is a more difficult topic that we should probably keep for > another day.
The vibe-code problem looks like a specific instance of the growth problem to me. There are two kinds of grows: growth in size at constant complexity, and growth in size and complexity. Automation works great for the first kind. For Guix, that would be a growth in packages that are unrelated to each other. But that's not the situation we have. What we have is growth in size and complexity. On the technical level, more packages that are increasingly interdependent. On the social level, increasing divergences about which software is "good enough" (by various criteria) to deserve a place in Guix. Today's channels are somewhat like coarse-grained packages. Somewhat, but not enough to allow the same freedom of combination that is available for packages. But the overall idea of adding a level of hierarchy looks promising for managing increasing complexity. Cheers, Konrad.
