

But we know why Snaps and Flatpaks started existing. I also think they are architecturally ugly.
And I think you have a point in terms of patches potentially coming too slowly onto an immutable system. But that problem isn’t an inherent one, it’s just a problem if distribution updates are slow because community support is lacking. At which point you’re just trying to compare Open Source to Proprietary solutions where support is explicitly paid for. I’ll trust a year old Linux kernel over the latest and greatest Windows release any day.
I love The Debian Project as an entity and I hope it exists until the end of time. I have this old 2005ish Sony Vaio which was built right at the cusp of the switch to x64 and thanks to Debian (who I believe are the only ones who still do 32 bit builds) I was able to bring my nostalgia for the device into a modern age. But I digress.
I think ultimately we need to find a way to make dependency conflicts a thing of the past. Just install two versions of the same library if 2 of my programs need different ones. Maybe I’m thinking too naively about this and of course this isn’t something you could do on an immutable system, but if we’re talking Linux as a concept there are definitely some common practices today no one would’ve even considered 15 years ago. We need to make it irrelevant whether my installer is called pacman, zypper, apt, dnf or what have you. AppImages can give us that freedom and portability right now. Maybe we could combine the convenience of packaged apps with the beauty of centralized package management.