• Urbeker@beehaw.org
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I’ve found flatpak to have taken several design decisions that almost seem tailor made to make it hard to use. I use an app launcher as I use I3 to run apps, except I can’t use it for flatpak because it doesn’t just make stuff available on the path, I’d have to make a wrapper script or something at which point I’ve decided to use another app or package. It also had an issue where everytime I got a gpu driver update it updated every single flatpak fair enough but it kept all the old versions! It was using double digit percentage of my disk for no reason, and the response on issue for this on the repo was just this is intended behaviour.

    If it wants to get mass adoption they need to work on letting it get out of the way of people trying to use it.

  • Yozul@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I think Flatpak is already good enough to be useful, and improving fast enough that it might be viable as the default way to distribute graphical apps for the majority of distros in the nearish future. I personally still prefer native apps, but I recognize those inherently involve massive duplication of effort, and that effort could be much better used in other places. If we’re going to move to a universal packaging format, then for me personally Flatpak seems like the clear winner already, and that gulf is only widening. I just hope it doesn’t stay so centralized around Flathub.

  • donio@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I am usually not a huge fan of such tools but I am kinda ok with flatpak. The fact that it doesn’t need a daemon (or even root) and the relatively sane CLI makes it passable and I use it when the alternative is more painful.

    One particularly fitting use case seems to be managing non-Steam packages on the Steam Deck. It funny to see non-Linux users managing to install and use all kinds of stuff through it.