More than 2GB for a colorpicker? #flatpak can be a pain in the ass if you have 5 apps, that have 5 different platform dependencies. #linux #gtk #gnome

@owzim

that's so stupid and this is why I hate flatpak

@selea Depends I guess. I just installed it with nix package manager in like 10 seconds. To be fair #flatpak covers additional stuff like permissions and sandboxing.

@owzim @selea your nix installation also has these 2GB downloaded, you just already have them installed in a previous update.

also that dialogue saying it will install 2GB is afaik just a projection, meaning, that it might not do that, as it can only figure out the actually sizes on install/download, as it deduplicates.

@razze @selea that might be true, but it comes down to how it feels. I perceive flatpak installations as very slow and very huge and all in all clumsy. Not so with nix. #shrugs

@selea @owzim

I think it's not too stupid, it's just a consequence of wanting a package format that works on all linux distributions. AppImage and Snaps have similar (if not worse) disk space requirements.

Sure, you can say that OS packages take less space, but those have their own set of issues.

@ainmosni @selea @owzim I bet lots of us can agree that ...

sometimes it's smart to be a bit stupid ... and sometimes it's stupid to try and be too smart! 😃

@owzim Those numbers are pre-install, and theoretical maximums, not the actual amount downloaded (hence the "less than" sign in front). Chances are (given some of them are marked "u" for "update") you already have the packages, and will get a smaller delta. So unlikely to be a full 2GB download for you.
@owzim That's because you're updating the platform libraries at the same time. The actual package is less than 3MB.
It's also available in some repositories, such as nixpkgs and the AUR, although neither are officially supported.
@FineFindus of course it's not the size of the package but of the dependencies. the outcome is the same. it's huge.
@FineFindus thanks for this nifty little tool btw. It was not to bash your app in any way but question the concept of flatpak in certain cases. I installed it with #nix in no time, without any issues.
@owzim It's always super nice to hear that users like the software I make, thanks! Let me know if you have any more feedback :)
Also, are you just using Nix, or are you using NixOS? If the latter, would you mind answering a few questions about it? I'm trying to evaluate switching to it.
@FineFindus @owzim i think you're both right… but at the same time the first user's complain is closer to the normal flatpack usecase, so while the download/installation size will not repeatedly be that huge, it still will be considerably higher than in yours. otherwise the very central idea behind it woild not compete against a system-wide library set. imho of course.
@FineFindus @owzim this is of course different (expectedly so) on immutable systems where a package manager is basically replaced by flatpack… while the nature of the approach keeps the libraries… less scattered over the «version landscape» i guess.

@owzim

Disk space can be a problem if you're only installing one or two #Flatpak applications (which, by chance, will use two different runtimes). If, like me, you have more than sixty applications sharing a small number of runtimes, it's less of an issue.

I also think that distributions designed from the outset to make massive use of Flatpak (like #Fedora Atomic Desktop) will be even less problematic in the future.