GitHub - trytomakeyouprivate/dont-use-appimages: Appimages are an insecure packaging system with very limited use cases. Please use Flatpak instead!
github.com
Appimages are an insecure packaging system with very limited use cases. Please use Flatpak instead! - trytomakeyouprivate/dont-use-appimages

Appimages totally suck, because many developers think they were a real packaging format and support them exclusively.

Their use case is tiny, and in 99% of cases Flatpak is just better.

I could not find a single post or article about all the problems they have, so I wrote this.

This is not about shaming open source contributors. But Appimages are obviously broken, pretty badly maintained, while organizations/companies like Balena, Nextcloud etc. don’t seem to get that.

  •  Pantherina   ( @Pantherina@feddit.de ) OP
    4•4 months ago

    You shouldnt need Flatseal as Flatpaks should have as little restrictions as need to make them work properly.

    This is an app problem, on Android all apps start with 0 permissions and many work completely without.

    I maintain a list of flatpak apps following modern standards. Those dont just work because their sandbox is full of holes, but because they are adapted to use portals etc.

    So Flatseal is used to harden flatpaks, not weaken them, normally.

    that it would make my backups and restores take 900% longer and would rinse my data when they need updating.

    You mean their storage space? Yes, biggest problem. Not very well solved tbh compared to android where all apps are also sandboxed but they have sizes of 30MB or something.

    Flatpaks should be preferred over many other formats though, as they just work, dont touch the system and are more secure, unlike Appimages.

    I highly recommend to watch this talk that some commenter mentioned

    https://www.youtube.com/watch?v=b4_TXZJw3rU

    •  Churbleyimyam   ( @Churbleyimyam@lemm.ee ) 
      2•4 months ago

      Thanks for the links. I really want flatpak to work for me because I like the sandboxing but the storage thing is a bit of a killer for me at the moment and I could not for the life of me get Digikam, Shotwell or Rawtherapee to hand image files over to GIMP with the flatpak versions, whereas the repo versions were fine out of the box. Also, I feel like flatpak programs are much slower to open but that might just be me.

      •  Pantherina   ( @Pantherina@feddit.de ) OP
        1•4 months ago

        Flatpaks will always be a little slower, notably if you are on slow storage media.

        Yes this is all native messaging I suppose. Flatpak apps can query an app list, just look at flatseal. So I think querying the installed flatpaks and handing it over to the system portal where you then choose the desired app is the modern workflow for this.

        You might want to request that Digikam etc. implement portals for this file opening. Firefox can do for example but of course these are limited as long as apps dont modernize their workflow

        •  Churbleyimyam   ( @Churbleyimyam@lemm.ee ) 
          1•4 months ago

          I do hope flatpak can solve these things. I have the deb installs all working harmoniously at the moment, so I don’t want to touch them but will have another look at flatpak versions at some point in the future.

          •  Pantherina   ( @Pantherina@feddit.de ) OP
            1•4 months ago

            Downstream Distribution is simply very very work intensive. By having the system and apps come from a downstream origin, packagers need to follow upstream and keep up with versions. And as upstream doesnt officially support these packages, many will have bugs. Or like on Debian, packages will be unusable as they are too old with unfixed bugs for years.

            Neither Android, nor Windows nor any other big OS do things that way, for a reason.