For simple “apps” it is fine, but my computer is not a phone and I don’t use it like one. I mostly don’t want simple apps that have their own little sandbox to play in.
I want full-scale applications that are so big they have to use system libraries to keep their disk size down. I also don’t want them in a sandbox. I want them to have full access to the system to do everything they need to do, I want them to integrate with far-flung parts of the system and other applications too. I only use applications I trust and don’t want them constantly pestering me about configuring permissions and access in just the right ways and opening all the right doors and ports and directories to make them work, I trust them by installing them, they have permission, and the easier they make it to access everything I will inevitably be asking them to access, the happier I am.
My practical concern with distribution methods like AppImage and Flatpak is that now I have to do a lot of extra thinking every time I’m installing anything. To pick how I’m going to install something, I have to solve the matrix of “what kind of distribution method do I prefer for this type of software” combined with “what distribution methods are available for this software” and “what versions are the available distribution methods for this software” and “what distribution method provides the best way for this software to get updates”.
In the olden days, when the distro’s package manager was the only choice, all I had to care about was “is it available in my distro” and the decision tree was complete. I appreciate all the availability of choice that things like AppImage provide, but it doesn’t actually make it easier for me, it just makes it easier for the packager of the software. They’re doing less, but making more work for me, as a user. Distro packages are a lot of work for the maintainer precisely because they at least make an effort to solve many of these issues for the user. The value-add that maintainers provide is real.
I couldn’t agree more. Occasionally I’ll use an appimage where something is not packaged for my distro version and I only need it temporarily.
Maybe I’m just long in the tooth, but linux used to be a simple, quite elegant system, with different distros providing different focuses, whether they were trying to be windows clones, something that a business could bank on being there in ten years, or something for those who like to tinker. The common theme throughout was ‘the unix way’, each individual tool was simple, did one job, and did it well. Now we seem to be moving to a much more homogenous ecosystem of distros with tooling that tries to be everything all at once, and often, not very well.
I agree, there’s a place for flatpaks and appimages, but for the most part my computer isn’t it. If I was setting it up as more of an appliance or as a work computer in a fleet of devices, sure they’d be great. I installed VLC in it’s flatpak form on accident once and it was worthless because the entire reason I installed it was to watch either a DVD or Blu-ray, and it didn’t have the libraries to read the disc. It took me far longer than I’m willing to admit to figure out it was because flatpak. I’m sure there’s a way to work around that, but at that point I was done with any flatpaks for anything that might need additional anything.
They do cut down on needing multiple versions of the same package, so I’ll sometimes install the flatpak version to try something out if I’m not sure it’s what I want.
At least for appimage, it doesn’t create application launchers. And it’s 50/50 whether the icon in the window list works or not.
I also build a lot of Docker images, and container formats throw a wrench in that if that’s the only way the application/utility is packaged. So I end up building from source.
It is CLI and I’m GUI by nature, but AM is easy enough for me. Just yesterday I did a simple
am -u and got the latest updated versions of qBittorrent, FreeTube, yt-dlp etc. (I.e. the kind of program that system packages are too out of date to work safely or even work at all.)
There are other options like zap (CLI), Gear Lever (GUI) and just recently I believe the Nitrux distro came out with a complete AppImage software manager. (Checking it out, https://github.com/Nitrux/nx-software-center , it seems it pulls from AppImageHub.com, which unfortunately has largely been forgotten by developers, a lot of software is either out of date, unverifiable or completely absent. AM is much more up-to-date, pulling the latest AppImages mostly from official GitHub repos.)
Let the hate of the crowd wash over me, but I don’t even like Flatpak, and I’ve got love-hate (mostly hate) relationship with AppImage as well.
Just give me a system package or a zipped tarball.
In recent years, have had to just get used to needing to build most projects from source.
Why the hate part of AppImage?
For me it is the “Windowsy” feeling of downloading an executable from some website. I prefer having all my packages managed in one place.
Makes sense, I kinda like it from a distributor standpoint. Flatpak is my favorite though.
For simple “apps” it is fine, but my computer is not a phone and I don’t use it like one. I mostly don’t want simple apps that have their own little sandbox to play in.
I want full-scale applications that are so big they have to use system libraries to keep their disk size down. I also don’t want them in a sandbox. I want them to have full access to the system to do everything they need to do, I want them to integrate with far-flung parts of the system and other applications too. I only use applications I trust and don’t want them constantly pestering me about configuring permissions and access in just the right ways and opening all the right doors and ports and directories to make them work, I trust them by installing them, they have permission, and the easier they make it to access everything I will inevitably be asking them to access, the happier I am.
My practical concern with distribution methods like AppImage and Flatpak is that now I have to do a lot of extra thinking every time I’m installing anything. To pick how I’m going to install something, I have to solve the matrix of “what kind of distribution method do I prefer for this type of software” combined with “what distribution methods are available for this software” and “what versions are the available distribution methods for this software” and “what distribution method provides the best way for this software to get updates”.
In the olden days, when the distro’s package manager was the only choice, all I had to care about was “is it available in my distro” and the decision tree was complete. I appreciate all the availability of choice that things like AppImage provide, but it doesn’t actually make it easier for me, it just makes it easier for the packager of the software. They’re doing less, but making more work for me, as a user. Distro packages are a lot of work for the maintainer precisely because they at least make an effort to solve many of these issues for the user. The value-add that maintainers provide is real.
It doesn’t sound like they’re making more work for you. It sounds like you’re making more work for yourself, and it sounds exhausting.
I couldn’t agree more. Occasionally I’ll use an appimage where something is not packaged for my distro version and I only need it temporarily.
Maybe I’m just long in the tooth, but linux used to be a simple, quite elegant system, with different distros providing different focuses, whether they were trying to be windows clones, something that a business could bank on being there in ten years, or something for those who like to tinker. The common theme throughout was ‘the unix way’, each individual tool was simple, did one job, and did it well. Now we seem to be moving to a much more homogenous ecosystem of distros with tooling that tries to be everything all at once, and often, not very well.
You’re looking for FreeBSD.
I agree, there’s a place for flatpaks and appimages, but for the most part my computer isn’t it. If I was setting it up as more of an appliance or as a work computer in a fleet of devices, sure they’d be great. I installed VLC in it’s flatpak form on accident once and it was worthless because the entire reason I installed it was to watch either a DVD or Blu-ray, and it didn’t have the libraries to read the disc. It took me far longer than I’m willing to admit to figure out it was because flatpak. I’m sure there’s a way to work around that, but at that point I was done with any flatpaks for anything that might need additional anything.
They do cut down on needing multiple versions of the same package, so I’ll sometimes install the flatpak version to try something out if I’m not sure it’s what I want.
So, vibes?
And the added work with keeping them updated.
Most update themselves & flatpaks are the worst when you need them to work with your system (ie: scripts).
So I guess your opinion is just wrong, sorry! (That’s a joke you guys)
I despised the Windows way of everything having their own updater either running in the background or only alerting you when you want to use an app.
AppImage to me feels like a big step backwards.
Damn, should have said that sooner, I see people don’t tolerate that kind of talking to others in here. Respect the community.
I know! All those down votes are really going to tank my Social Credit Score :(
Yes… good thing this isn’t reddit, right? :)
Interesting you compare it to Windows, given how in OS X you literally just drag applications into your Applications folder to install them.
Just not a fan of container formats in general.
I say that as a heavy user of Docker, but that’s a different use-case.
I go the opposite way. I like the ideas of container formats lol
deleted by creator
Not trying to be annoying like a kid here 😅, but why not?
At least for appimage, it doesn’t create application launchers. And it’s 50/50 whether the icon in the window list works or not.
I also build a lot of Docker images, and container formats throw a wrench in that if that’s the only way the application/utility is packaged. So I end up building from source.
Personally, I use AM. Takes care of that and more.
It is CLI and I’m GUI by nature, but AM is easy enough for me. Just yesterday I did a simple
am -uand got the latest updated versions of qBittorrent, FreeTube, yt-dlp etc. (I.e. the kind of program that system packages are too out of date to work safely or even work at all.)There are other options like zap (CLI), Gear Lever (GUI) and just recently I believe the Nitrux distro came out with a complete AppImage software manager. (Checking it out, https://github.com/Nitrux/nx-software-center , it seems it pulls from AppImageHub.com, which unfortunately has largely been forgotten by developers, a lot of software is either out of date, unverifiable or completely absent. AM is much more up-to-date, pulling the latest AppImages mostly from official GitHub repos.)
Missing dependencies. (Or wrong version of fuse)
I’d say that complete lack of a single consistent way to manage updates.
I really don’t feel having to micromanage each piece of software.
No automated updates has be the biggest reason for me.
I already have the system package manager. Everything else that isn’t it doesn’t manage my system and is doomed to suck.
If it’s not in Apt, I just run it in docker.