Why not snap?

I will use deepl again for this text, because I want to make sure that I am understood. Because I want to say a lot of things that the “hardcore linux users” would be outraged :smiley:

So, along with this thread:

I almost got a small heart attack.

For me personally, snap, flatpak and appimage is the worst thing that could happen to the Linux world. This just shows again that in the Linux community or in the developer community that make a lot for Linux, can never agree. Sure it makes sense in many areas to have a lot of choice. But in some (and especially those are often critical) areas that makes no sense at all. And often even, the “solutions” exist only because the developers are too stubborn or too lazy (or both) to stick to “the standard” or to agree on the most widespread. No, instead they cook their own soup…

But anyway, I find that sad enough. But if the day comes when more packages are delivered only via Snap & co (or only), then I say: Bye Linux. Hello Windows or macos (hackintosh).

Because exactly this shit is one of the reasons why I switched to Linux in 2006. I don’t want to have 3728952309 versions of “libraryX.so” in my system, all with different bugs and security holes. Not to mention memory consumption. Sure at that time it was more critical, because disks had rather around 80GB (which were affordable) and not several TB for under 100€. Likewise, I do not want that I have to update everything individually as in Windows. Sure that is solved with Linux then surely somehow about the various stores and package managers, but then you have sometime his browser as snap, his email client as appimage, then something else again as flatpak, etc etc. Incredibly complicated, incredibly fat, incredibly slow.

And what is all this shit for? Simple: Supposedly because this would be easier for the user. But that’s just a pretense, because the real reason is rather: much, much, much easier for the developers and for those who have to/want to manage a distribution. So the developers don’t have to worry about “libraryX.so” in version 3.1.2 only being available on Arch, OpenSuse and Debian. But not on Ubuntu and others. And they also don’t have to worry about whether the user has dependency XYZ installed. Or other packages that might be in conflict. And for those who have to manage a distribution, have a lot of work in the beginning, but once this “change” is done, the effort is just a joke.

Well. As I said, if in the future there should be no more Distribrution that approaches it “classically”, then it was for me.

For this reason I boycott e.g. balena etcher. Or all other packages that are extracted from snap, flatpak or appimage, just to save compiling.

But well, just my 2 cents.

Translated with www.DeepL.com/Translator (free version)