ax1900kr

  • 7 Posts
  • 46 Comments
Joined 1 year ago
cake
Cake day: July 12th, 2023

help-circle
















  • BC it’s easier for the any dev to package their program for flatpaks assuring it’ll work in all distributions, otherwise you have to wait for your package manager maintainer to repackage the program for your system. Which is what happens for Arch, debian, Suse, Fedora.

    It’s not Thunderbird/program responsibility if they decided to make flatpaks the main source of distribution yet you decide to install it through other means. Which idk if they did but more devs are opting to distribute through flatpaks.






  • Generally speaking, the advantages of Flatpaks are:

    -The developers only need to maintain and release one version

    -It’s sandboxed, for each app you can decide which parts of your filesystem are exposed, which env variables, which types of inter-process communications, etc

    -You kinda avoid dependency hell. You can use old unmaintained packages because Flatpak will provide old versions of their dependency if they’re needed, while at the same time avoiding unnecessarily duplicated packages

    -All installed apps are in your .var folder instead of being system-wide. Every app has its own folder with its own .config and .local/share inside, with their respective config files and data

    -It supports partial updates

    -It doesn’t require root permissions to use

    -It lets you use the most recent software even in really old LTS systems like Debian, and the Flatpaks updates are usually as quick as rolling release distros

    -You don’t need to abuse PPAs or the AUR

    -It makes your system updates actually faster since you’ll have less system packages, and you’ll be able to update your big apps separately

    I may be missing some, but those are the most important to me