138
Why Flatpak Won and Snap and AppImage Didn't. - Cameron Knauff (www.youtube.com)
submitted 8 months ago by to c/linux@programming.dev
113 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 89 points 8 months ago (47 children)

I like both flatpaks and appimages why does everything have to be a victory and defeat

  • permalink
  • fedilink
  • source
  • hideshow 47 child comments
    •
  • [–] 68 points 8 months ago (32 children)

    Because it's nice for devs to have a single package type to build per OS

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 32 child comments
    •
  • [–] 17 points 8 months ago (19 children)

    Why can’t they do that already? Just choose whichever one you want it’s trivial for me to run whichever as a user

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 19 child comments
    •
  • [–] 32 points 8 months ago (9 children)

    Just not snaps.

    AppImage and flatpak are fine though

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 9 points 8 months ago (7 children)

    Whats wrong with snaps? My only "issue" with appimages is i tend to leave them in my downloads folder and lose them

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 19 points 8 months ago*

    The snap store is a shit show of security issues.

    Forced migration to snaps.

    Performance issues.

    Proprietary back end.

    Slow to install

    Slow to start

    Eat up RAM

    Eat up disk space

    They screw up access to devices.

    They automatically update themselves without user confirmation.

    Fuck snaps. Fuck Canonical.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 8 months ago

    There's an appimaged daemon you can install that will manage them, and it watches a bunch of folders to integrate appimages with xdg and whatever window manager you've got. ~/Applications looks like an easy pick, or ~/.local/bin.

    Appimages you decide to keep you can just move there!

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 7 months ago

    That's why I whenever I download an appimage that I intend to use somewhat regurarly, I typically make a .desktop file for it in /usr/share/applications so it shows up in my app menu or rofi or dmenu or whatever and I don't have to go looking for it. It also helps to have a folder you toss them all into

  • permalink
  • fedilink
  • source
  • parent
  • [–] 9 points 8 months ago (8 children)

    Recently I wanted to uninstall $thing. Couldn’t via the package manager. I had forgotten that it wasn’t a native package. So what was it? *scratches head* Flatpak, snap or Appimage? Aw damn, it’s an AppImage. Now where did I put the binary? *scratches head*.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 10 points 8 months ago (2 children)
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 8 months ago

    Maybe you would like appimagelauncher. It allows you to define a directory for storing your appimages and you just put them in there and you can automatically launch it from the system menu as if they were installed apps. It also makes removing them easier, since they're all in the same directory and you just remove them and the shortcuts get deleted as well

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 8 months ago

    The fluxer appimage will 'install' itself into /opt/ without your knowledge. I think because it's essentially an electron package similar to stoat, standard notes and discord, large parts of it can self-update without needing to bump the actual package version, but this is really shitty behaviour considering what appimages are designed to do.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 8 months ago (9 children)

    Yeah, it's called .deb

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 6 points 8 months ago (8 children)

    Well that's not gonna work on rpm based distributions now is it

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [+] -7 points 8 months ago (7 children)

    How is that my problem

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 14 points 8 months ago (6 children)

    How is that my problem

    Well let's break it down...

    You thought:

    Yeah, it’s called .deb

    Was an acceptable response to:

    Because it’s nice for devs to have a single package type to build per OS

    Your problem was your stupidity.

    But now your problem is everyone knowing about it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] -5 points 8 months ago (5 children)

    Jesus fucking Christ, it's like you had your sense of humor surgically removed.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 8 months ago (2 children)

    I think you're the one lacking a sense of humor if you thought your comment was funny instead of making you look like an ass.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 12 points 8 months ago (6 children)

    It goes a long way to simplicity from both a user and dev to have only one package type to deal with and distribute.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 5 points 8 months ago (1 child)

    I'd agree with that sentiment, but at least for me, if we went with all flatpacks, i'd be losing the one ability that I like about appimages, which is as a one-time-use type of "installation". They're kind of like those windows EXEs that you could just run in place without needing to install. very useful for stuff like raspberrypi imager where I don't need to keep it around much

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 6 points 8 months ago

    appimages also allow some sort of portable apps you can carry around. Very useful for dealing with no internet scenarios. I also use appimages for things iI use very rarely and don't want to bother to have them being updated regularly along with the system

  • permalink
  • fedilink
  • source
  • parent
  • [–] 7 points 8 months ago* (3 children)

    This completely. Speaking as a person who's more tech skilled than 99% of non-programmers, i can tell you that installing apps is the main tech hurdle for Linux getting mainstream adoption.

    There are non-tech hurdles too, but of the actual technology being easy to use then app installation is really the only aspect left that regular people can't do without a huge dive of tech learning that's beyond what most people can do.

    • Installing on mac: click the Mac download button and follow the prompts.

    • Installing on Windows: click the Windows download button and follow the prompts.

    • Installing on Linux: there's no Linux download button, there's a couple of buttons that say words you've never heard of before. They look kinda like buttons to download an app. You click one and try to open it, but it just shows an error, etc etc etc

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [+] 2 points 8 months ago (2 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 8 months ago (4 children)

    why does everything have to be a victory and defeat

    there can only be one standard.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 8 months ago (3 children)

    But what if it doesn't cover my specific usecase?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •