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

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 37 child comments
    •
  • [–] 20 points 6 months ago (24 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 24 child comments
    •
  • [–] 36 points 6 months ago (14 children)

    Just not snaps.

    AppImage and flatpak are fine though

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 14 child comments
    •
  • [–] 9 points 6 months ago (12 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 12 child comments
    •
  • [–] 20 points 6 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
  • [–] 6 points 6 months ago (4 children)

    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
  • hideshow 4 child comments
    •
  • [–] 1 point 6 months ago (3 children)

    Why do you keep appimages? I don't do that and now I'm wondering if I do something wrong. But I try to install from repos as much as possible.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 6 months ago*

    I've used one or two tools that only distribute for my system as an appimage or as source code.

    I can't always be bothered to set up a compilation environment or deal with removing dependencies.

    I only use one or two regularly, but it's nice to have them integrated!

    I prefer from the distro's repos, then source, then flatpack, then appimage. Sometimes you have to take what you can get!

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 6 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
  • [–] 10 points 6 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
    •
  • [–] 11 points 6 months ago (2 children)
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 6 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
  • [–] 4 points 6 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 6 months ago (9 children)

    Yeah, it's called .deb

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 6 points 6 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 6 months ago (7 children)

    How is that my problem

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 13 points 6 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 6 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 6 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
    •