Flatpaks

[DavidMcCann]

Not so much a problem, more of a rant. I've never used flatpaks or any other system that mimics Windows, so this was my first experience. I installed Wine. The download was 1200 MB — I could hardly believe it, since that was almost 10 times the Debian package. After making sure that it worked, for both 32-bit and 64-bit programs, I deleted it and tried another new experience — a SlackBuild. I didn't keep track of what it was doing but I ended up with just 256 KB of installed files. That too worked. It seems my distrust for flatpaks was justified.

[DidierSpaier]

Not so much a problem, more of a rant. I've never used flatpaks or any other system that mimics Windows, so this was my first experience. I installed Wine. The download was 1200 MB — I could hardly believe it, since that was almost 10 times the Debian package. After making sure that it worked, for both 32-bit and 64-bit programs, I deleted it and tried another new experience — a SlackBuild. I didn't keep track of what it was doing but I ended up with just 256 KB of installed files. That too worked. It seems my distrust for flatpaks was justified.

Yes, flatpaks are huge. This is because installing one triggers installation of all their dependencies as other flatpaks, and is the price you have to pay to be able to install and run them on almost any system. But note that if you install one more that has the exact same dependencies you will not have to install again these dependencies. At the end of the day, installing a flatpak, an Appimage or an application available for your distribution (if there is one, or if you can build and package one) is up to you. I wrote something about that here: https://slackware.uk/slint/x86_64/slint ... ADME.Slint