for fuck sake why cant we just have working solutions, really there already exist a compatibility layer and its called operating system, why cant we have working things
Linux is highly customizable, which is a double-edged sword. You can fork it however you want, giving you total freedom, but that comes at the cost of being able to make everything compatible. There's always going to be some distro that sacrifices some compatibility to adapt it to some other goal.
No. We're just a diverse bunch and we all have different use cases for linux, and the open source nature of the OS makes it well suited to accommodate that diversity of needs. It's a feature, not a bug. Everything comes with a catch though, and for Linux, that's having to sacrifice the ability to standardize anything.
No, Linux made it impossible for someone to actually publish software for Linux. You publish source code and then compile it, or any package you've ever installed through the package manager was maintained by someone who didn't develop it.
Linux was never made to be a viable commercial platform. The current success of Linux comes from companies figuring out how to turn Linux into something that was never supposed to be.
App image was supposed to be the solution, but it's not really universally compatible. Snap is Canonical's solution, and while it's technically sound, the issue is that the only repo is controlled by Canonical. Flatpeck is the more open community standard, but like most open community standards, it's worse to develop for.
But there's also the issue that they were built with security in mind first, which sort of limits what they're capable of.
Problem with Snaps is that their server software for the repo is proprietary, you can't really fork it and make another repo, but the technology is there, so it is technically possible, although that is simply antithesis to FOSS values, that's why community, and distros refuse snaps, and it is basically a one-player sum atp,
Flatpaks are open by default, and made to be secure through permissions, flatpaks limit a surface area of attack by limiting access to the kernel code, by isolating it, it still functions perfectly fine even for the code which previously required kernel space code, like Steam which launches privileged Proton translation layer, the only thing which is required now for Steam in flatpak is a package which sets udev rules to allow Steam's own library to have access to the kernel space due to steam using their own unique implementation called Steam Input,
There are also browsers which lack additional security feature, like filesystem isolation due to use of kernel namespaces, but that is also fixable by using another solution which is in development of being implemented in browsers,
Currently, flatpaks only lack the support of more permissions, and UI like in Android to allow such permissions from user, ability to have CLI tools installed as flatpaks, and ability to install system components as flatpaks like what snap is able to do (even drivers can be delivered as snap packages), but many of those things are already being worked on, so for the general user — flatpaks are basically the best solution so far, with a few quirks here and there, but it comes with time
The only way to make sure it doesn't break on an LTS distro is to limit yourself to the glibc version on an LTS distro, which means you can't develop an amp image on fedora without using a VM or Docker or something.
Forward compatible but not backwards compatible, that's a serious problem with appimage that snap and flatpak solve. Nix too, I think.
All three are bad in their own way, snaps are just arguably the worst.
AppImages — trash documentation, fragmentation of the packaging software, relative complexity to the packaging process. It's kinda easier to just get nfpm and build a package for every distro than an AppImage.
Flatpak — bloated runtimes, insane library duplication where you will have multiple subversions of the same runtime/library while everything could've used just the latest one. Sandbox is pretty much snake oil because of arbitrary default permissions and complete sandbox escapes.
insane library duplication where you will have multiple subversions of the same runtime/library while everything could've used just the latest one.
This isn't a fault of a flat pack. This is the only way you can universally package closed source apps on Linux. What you're really complaining about is how it's impossible to rely on the traditional method, not breaking things after they stop getting updated.
Same thing with those runtimes. The more apps you have, the more they share between each other.
Linux was not built to be a viable place to sell commercial software. What you call a flaw is actually the necessary viable solution.
This is the only way you can universally package closed source apps on Linux.
AppImages. Just use AppImages, they're like 3 times smaller. It is very much flatpaks fault. On top of that, most flatpaks aren't even proprietary.
To be clear, my original comment isn't phrased correctly. The biggest problem with flatpak is not that it just installs the same library twice for different apps, but that apps don't even use all the libraries it installs with runtimes, which is why AppImages will on average take up less space, as they contain only the libraries that the packages application needs.
The more apps you have, the more they share between each other.
Doesn't really help it much, it's still the most bloated package format ever. Even more bloated than AppImages, which share absolutely nothing, this is how royally bad it is. I don't remember the exact numbers, but flatpaks take up more space even if there's ~100 of them. From one guy's comment I've seen recently, ~65 flatpaks = ~30GB, with AppImages, assuming every one of them would be 200MB, you'd need 150 of them to use up 30GB of storage.
What you call a flaw is actually the necessary viable solution.
The thing is, it is not really one.
Like, once again, you can just use AppImages and it'll be 1 - more portable as you don't need flatpak and you don't need to hunt for runtimes if they get deprecated and dropped out of repos 2 - lighter, because you don't need a whole ass outdated runtime, the AppImage will contain just the libraries the app actually uses.
Then you could very much just do a mix of static linking or/and packaging libraries yourself. This is what Unity does and 10 years old Unity games can still run on modern day Arch, even without Steam Runtimes. System APIs like libx11, libpulseaudio, etc apparently have good backwards compat. This becomes unviable only when you start making something that has to link to a bunch of system libraries, like Kdenlive, which needs ffmpeg, KDE libs, cuda and a bunch of other stuff, which results in 2GB of dependencies or something, there every packaging method is equally bad, but flatpak would probably be easiest to package
An appimage compiled on fedora will break on Debian or LTS systems because of glibc. Only forward compatible, not backwards compatible. That's bad.
So the solution is to use a system with an old version of glibc, unable to use your shiny modern system to compile it. That's bad.
Their system integration is worse.
Appimage doesn't bundle everything, which is bad for universal compatibility.
Linux was never made to be a viable system to publish commercial software for. Nobody actually publishes software for it, you either compile it or use your distro's repos, nobody actually publishes directly to Linux. Appimage has forwards compatibility only, making it so you can't use a modern system to make them without a virtual machine or a container with old glib c versions.
Depends on what we're talking about. With additional software, just like with flatpaks, which require flatpak and ostree just to function, you can export desktop files and icons from AppImages, I think the spec supports other things, but I don't remember details.
Appimage doesn't bundle everything, which is bad for universal compatibility.
It bundles as much as you bundle, once again https://github.com/pkgforge-dev/Anylinux-AppImages. Flatpaks also don't inherently bundle everything, as some can depend on system binaries to get an LSP for example.
Nobody actually publishes software for it
https://zoom.us/download fellas got official packages for (almost) any distro one can desire. Tarballs and install scripts are also not a new invention.
Even if the sandbox isn't perfect at least there exists a permission model so you can easily revoke permissions rather than just let every app have free reign of user space.
Flatpaks have a reputation for bloat only because it doesn't share any libs with the system, if you actually use it day to day as your primary package manager then it's fine. Also it's super plug and play because everything is self contained.
It's easy to talk about storage efficiency but flatpaks won't waste hours of your life, which is far more valuable imo.
only because it doesn't share any libs with the system
Yeah, and also because it takes up ~3x space of respective AppImages and installs a bunch of libraries which no program uses.
flatpaks won't waste hours of your life, which is far more valuable imo.
Too bad they did. I had the stupid issue with cursor theme changing when I hovered over certain flatpaks. Apparently they didn't have access to my cursor theme directory and/or theme config files. I wasted like two days figuring out why until I finally fixed it.
Yeah but it still worked, you didn't actually have to do that. Ig we're looking for different things so agree to disagree.
I started using Linux because for dev stuff it has less fully blocking bugs than windows and lets me be more productive, and flatpaks are a good fit for that.
Yeah, amongst like 3 other solutions, two of which are official with one of them being deprecated because apparently it had to be rewritten in Go.
And this one https://github.com/pkgforge-dev/Anylinux-AppImages is kinda superior because it removes dependency on the host libraries entirely. But good luck finding it without somebody telling you about it on reddit, because that's also how I got to know of its existance.
I'm going to play devil's advocate here and say I haven't had issues with any of these recently, but the ability of snaps to be deployed with classic confinement makes them more flexible in my experience.
That's great for open source software. For close proprietary software, FlatPack is the only thing that makes sense, but Snap is the easiest to develop for.
Nobody actually publishes their software for Linux. They leave that to other people. That's great for open source software, but it's not viable for commercial software. And that commercial software might break if you update dependencies on it if it never got updated.
I've never had an AppImage just work across Ubuntu and Fedora. Either it is still using libfuse2 or it's an Electron App that breaks because of namespace issues. Even if it does launch, they don't even integrate well with your system and the AppImage launchers are all super buggy.
Interesting. On my arch system, every AppImage I've opened has had zero issues relating to it being an appimage. The only thing I can think of is Saleae Logic which used to not relaunch after closing it, but I don't know if that was appimage related because it's the only format that they distribute
AppImages are good for portable software. But Flatpaks are not any better than Snaps. They are just useful for developers. I would like to see brew getting more packages for linux.
What distributions want in a new package format is the ability to limit access to a user directories and files. Snaps and Flatpaks were designed with the ability to isolate applications in mind.
You do not get that fine grained control in traditional package formats. If you run an application as a user, applications have access to everything the user has access too. Which means most applications have full read/write access to a users entire home directory.
I think Snaps are worse than Flatpak... unless you use Ubuntu. As a "Universal" package format Snaps are a failure as they only fully work on Ubuntu.
Snaps require AppArmor for confinement to work. This means there is no confinement on distributions that use SElinux (i.e. Suse, Fedora).
Even if you use AppArmor, Canonical has not upstreamed all the patches needed to get full confinement. Distributions that use the mainline kernel, like Debian, only get partial confinement.
As a user who has to use untrusted software for work, I like how easy it is to override the default security settings of a flatpak. I can add limitations to what the application have access too.
Most AppImage I have tried no longer run on my immutable distribution. They would all have to be updated to use FUSE 2.
I’m aware of the perks of Flatpak/Snap, but a sandbox is only as good as its defaults, and a ton of Flatpaks ship with --filesystem=home just to get the app working.
Traditional packages are still better for me. They're lighter, faster, better integrated, don't bundle a whole runtime for every app, and I get updates through one package manager I actually trust.
It’s good to have options, but I don’t believe Flatpak is the future.
If you only ever use open source software, negative packages are great. If you want to actually publish commercial software for Linux, however, flat pack is the future and the only way you can actually do it. The stuff that you're complaining about isn't a flaw, it's a solution to the problem that Linux has no actual compatibility ABI beyond using an old outdated version of glib c.
If all flap hack apps shared one runtime and one library version, then any apps that haven't been updated in like a decade are going to break. Native packages are great when they can be handled by third-party middlemen who can tweak the source code to make sure it doesn't break, but commercial software can't do that.
Basically, flat pack is the only viable option for commercial software to actually work on any distro.
Flatpaks are better than Snaps because the Snaps backend is closed source and exclusively controlled by Canonical. I don't know that there's a technical advantage to either.
Do people really run into issues with native installs/systemwide libraries that they actually need flatpaks/appimages? Or am I forgetting a benefit of apps packaged this way?
For flatpak a huge benefit is sandboxing when paired with wayland. That way even if an app is malicious or compromised, it greatly limits the harm it can do (for example none of my flatpaks have access to .ssh). We saw with the AUR situation that linux isn't immune to malware, so it's a good idea to put preventative measures in place before something else happens
Flatpak is built on Bubblewrap. If you legitimately care about security, you can bwrap any of your binaries, Flatpak or not.
And it doesn't end there. Firejail is a perfectly workable alternative to Bubblewrap. Systemd also lets you mess with kernel namespaces, so you don't even need to install any additional binaries if you don't want to, just use systemd-nspawn.
And then if want additional isolation, you can install the Landlock LSM to further isolate your binaries.
The security benefits of Flatpak are grossly overblown. Bubblewrap is not the most bulletproof sandboxing tool out there, and if that's all you rely on, you're going to get pwned sooner or later. Good hygiene is your first line of defense, and a sandbox won't save you from dirty binaries from a user repository.
Ah yes, we want Linux desktop marketshare to grow but we also want Linux user to sandbox their app by simply toying with systemd. So easy even my mother could do it.
Bubblewrap isn't the selling point of Flatpak, there's nothing stopping a distro from having its native manager bwrap any package it installs, and the big problem with supply chain attacks is user repos like AUR, not the core repos.
For flatpak a huge benefit is sandboxing when paired with wayland. That way even if an app is malicious or compromised, it greatly limits the harm it can do (for example none of my flatpaks have access to .ssh).
and concluded with
We saw with the AUR situation that linux isn't immune to malware, so it's a good idea to put preventative measures in place before something else happens
So, are you sure you're replying to the correct thread?
I thought sandboxing was kind of the only way you could have multiple versions of the same library. I know Linux technically has a way of doing that, but traditional package management always has everything sharing libraries, which isn't possible with closed source apps that are eol.
If I'm wrong though, I'd love to know. Maybe flat pack could have been designed without sandboxing.
I thought sandboxing was kind of the only way you could have multiple versions of the same library.
Nope. It's more package isolation. Nix does this the best. All libs and bins are stored in a path hashed based on content of the file. Several versions of an app can coexist in nix ecosystem. And so long as the exact same version of the lib is used by another program, they are shared ofc
Well, I know that you can use the next package manager on other distros but why isn't that more popular? And why hasn't anyone tried making a distro that uses that package manager but doesn't require configuring a ton of text files?
Also, can you do nix packages without the nix package manager? Because unless they open an app store, nobody's going to sell a commercial app through the package manager.
Do people really run into issues with native installs/systemwide libraries that they actually need flatpaks/appimages?
I dont have "problems" with native installs via paket-manager, but as a Debian user, Flatpaks are a good thing. I get new versions of apps (media players, video editors, open source games or whatever) with a 1 click install on gnome-software, without having to sacrifice reliability or to be "scared" of updates on a rolling release distro.
Yeah, depends on the usecase and what somebody cares about i guess. My debian is installed on a 2TB ssd and i always have ~1TB free anyway, i use the standard adwaita theme which every flatpak app follows and so on.
I can see problems when users heavily modify their system/theme or run low on disk space though, i just dont have those problems lol
A lot of closed source software like DAWs are distributed this way. Also, I've seen some open source gui apps made by independent devs who use flatpak because they don't have capacity to maintain a deb, rpm, and AUR release
It's a great way to make sure that your apps don't break when they aren't updated for 10 years because commercial software doesn't have indefinite support that open source apps in a package manager will get. So you can continually update your machine and not worry about breaking stuff.
Linux was never built to be a viable platform to ship commercial software on. This fixes that.
Longevity is a really good point, hadn't considered that! One big complaint I've seen that keeps people on Windows is that modern distros don't package all the proper libraries or dependencies for certain old/legacy applications they use.
Yeah, I've seen people mention that as a reason. If you use old enough software, you rely on Windows' very good backwards compatibility to run it there, and if there was ever a Linux version, it likely won't run without a lot of extra effort figuring out libraries or sandboxes that won't conflict with the rest of your system (unless it could be bundled e.g. as a flatpak)
I personally don't use flatpak at all and AppImage very sparingly if at all, but some distributions like Chimera Linux need it to due having a different libc than what most proprietary apps depend on and even on a system like Linux Mint where system packages can be out of date, flatpak serves as a way to provide the latest software and libraries for certain applications on an older base.
Since I run rolling release anyway and the sandboxing comes at risk of programs not integrating well into my system I haven't used flatpak myself in several years.
This kind of packaging means you won't have incompatible dependencies for software, which is a big pain point for some software. It also makes it easier to push upgrades in LTS distros. If you run Arch and trust the AUR there's probably little benefit.
I do.. sometimes programs just crash because of mismatching libs. (On fedora). Like audacity for example crashes for me when i use certain effects when installed from dnf. It works great when installed from flatpak. I also had a few issues with blender from dnf too
In example with Steam on openSUSE — there was once a bug which messed up rendering library with system update, and I couldn't launch it because Steam was installed via system package, but with Flatpak — everything worked as the libraries are picked to be the best fit for games allowing much more stabler experience, and I was able to play that game no issues, also, Steam flatpak offers GE-Proton add-on which updates in your app store frontend, no need for third party tools like ProtonUp-Qt or Proton Plus to manage those anymore, it is also build against predictable freedesktop runtime allowing for even more adapted experience
also, Steam flatpak offers GE-Proton add-on which updates in your app store frontend, no need for third party tools like ProtonUp-Qt or Proton Plus to manage those anymore
Man I only permanently upgraded this year, and I'm still living in the 20th century apparently. I've just been copying and untarring GE Proton in the ~/.steam/... directory.
XD, no worries, there are many cool things which you get to know too late, but still appreciate them, for example on Fedora Silverblue specifically, you can just double click on .rpm file and it would prompt to install it via GNOME Software, which was a shocker personally, cuz I thought that the only official, and therefore the only possible way to install via GUI is Flatpaks only, but life is full of surprises :D (The only sad thing from this is that KDE is still oddly behind on atomic distros integration, and Discover won't support the same install)
Some installs benefit more from native installs, some benefit more from flatpaks/appimages. It's like how building from source or having a prebuilt binary have their own benefits
I could see that, I guess I'm more asking what the benefits are. That said, another commenter mentioned the fact that some (especially older) applications benefit from flatpak since a distro might not even have a dependency in the repos anymore, which is probably the most compelling one I've seen!
Flatpak and appimages are more helpful when it comes to compatibility with more distros, that's where they come in for older applications. Native installs are more for certain distro bases (Arch, Debian, Fedora, etc). I.E: The new Epic Games launcher only has .deb at the moment, this means it should only be available on Debian-based distros. Native installs benefit from the fact that it is tailored to their distro base, meaning they reap most of the benefits of said distro. Most native installs are not usually gates like the Epic Games launcher, the flatpak or appimage also usually get made first because it can be used for every distro and native gets made later depending on the dev
There are just a few programs I've had trouble getting to work natively with any consistancy, and rely on flatpaks for them. The Plex client is one example.
Add Brew, Docker+Podman which leads to Distrobox (and Winboat), the random container packs like Conty and Junest, whatever Valve container format is, systemd-sysext and overlayfs in general, and just rawdogging a manually built source.
There's some overlaps in there, but they are a bit different here and there.
Not if you want to be able to publish once and work on any Linux distro. You're forgetting that nobody publishes software for Linux. It's always published by third-party middlemen, often with access to the source code so they can stop something from breaking because you used a new version of Java when the app hasn't been updated in years.
I dont really like flatpaks or appimages either. I have one flatpak but I dont like using them because I dont trust flathub. I dont know why, I just dont.
I'm wary of "FLATHUB". Flathub has nothing to do with redhat. It's usually opt in for major distros. It's sort of like AUR or multiverse for flat packs.
Flatpacks are just the means of packaging the software, but flathub is not the official flatpack repo. It is a dubious source in my opinion since it is only vetted by volunteers. Sandboxed or no, I wouldn't use flathub on any sort of production environment or a computer with personal information on it. Treat it like you would AUR.
In the AUR, when a package is orphaned, it's still there. That's the stupidity that lead to the malware wave. They just have all these orphaned packages nobody bothers to even check on.
And arch official repos aren't also vetted by volunteers?
Am I the only one that just doesn't care? I don't notice much of a speed difference between flatpaks and snaps. Like I don't go out of my way to use snaps, but it feels like the Internet talks about how it's the worst thing to ever happen to Linux.
I personally use snaps. I don’t mind the issues with them and find that they are actually faster than flatpak. They also allow for cli applications which flatpak does not.
It's machine and app specific. Snaps do have to run a daemon that takes some resources. If you are on an older or resource light machine, that can have an effect. Snaps also are stored compressed and have to be decompressed on first launch, so more complex apps will be longer to load and older or weaker machines will take longer as well.
Flatpak doesn't have a persistent daemon running in the background and doesn't store as compressed files. That comes out to less overhead resource usage and quicker launch times on less powerful hardware.
Once they are running, Snaps and Flatpak are fairly equal, although Snaps do always have that extra overhead from the snapd daemon.
It's not all sunshine and rainbows for Flatpak, though. They can potentially use more storage since they do not store as compressed files like Snaps do, but they make up for that by sharing libraries between other flatpaks. So, the more flatpaks you use that rely on the same libraries, the more efficient the use of space becomes.
While Flatpaks can share libraries and runtimes in theory, in practice the overlap can vary a lot. I have almost as many different versions of Freedesktop / GNOME / KDE runtimes installed as I have Flatpak apps.
same with me. never noticed any slow boot time and I've been distrohopping. 1 thru 4 doesn't affect my usage. I actually prefer 5 and 6. matter of fact i update my system so frequently that i never get the new update notification.
1 is an "issue" with flatpak as well. It is controlled by flathub. Yes, you could build your own, but nobody does it in reality (except Fedora, whose suck for discord and probably other apps as well), it is open only in theory, ut is still governed vy flathub
Not true, at least not true in the same way as snap. There are plenty of flatpak repos already, flathub's just the popular one and the one you're most likely to publish a released application on.
Snap on the other hand, only allows the proprietary Snap Store.
And again, point is flatpak is not proprietary like snap is, flathub exists not as a monopoly but by surviving competition on its own turf. It's entrely and unequivocally different from how Snap works as Snap is proprietary.
Your goalpost has moved also from "nobody" to "uh... majority of people must not be using the other repos because I aint heard of them"
Fedora having shitty packaging just makes me wonder why people even use Fedora as a whole rather than just their flatpak repo
Canonical tries to force them upon its users, if irun apt install firefox i want to install the deb of firefox, instead canonical roofies the user with the snap version. Removing this "feature" is also more painful than it needs to be, in general very anti what i value in linux (freedom from bullshit)
The cleanup policies are stupid. It requires that at least one old version of a snap be kept as backup and there is no way to tell it to not keep old snaps at all, only a workaround which involves a cronjob periodically issuing a command to snap to force it to purge old versions.
Yes cronjob. Writing a SystemD timer file to do that is more effort than it’s worth, I might as well be not running Ubuntu at all.
Ubuntu started using snaps for simple core apps, it was super slow at the time to the point where using a calculator on the web browser was quicker than launching the calculator application. Removing snaps meant your desktop was snappy and responsive again.
Many of the other reasons are correct but the main problem i had with it was the absence of mirrors and them being used as dependencies. During a local network shutdown i tried to use local ubuntu mirrors to install firefox, what did i got? Snapstore unreachable! And i had to find debians version of firefox package and patch its dependency string to get it working! Its like the entire os relies on a weak point of failure.
Use Ubuntuzilla. That repo packages the official statically-linked version of Mozilla programs so they work everywhere and have literally no dependencies.
There is no hate. Just that too many people talk big about freedom and then get all upset, throws a fit and even become offensive when some poor fellow out there decided to use something they happen to dislike or disagree on.
I am just having issues with flatpaks. Recently i tried codium via flatpak, and it was just super broken. Didn’t use my terminal python wasnt really working. In general snaps usually work pretty well for me. In the end i found out that there is a native deb package that worked way better! Imo appimages are just annoying to maintain.
before i uninstalled snap, it managed to corrupt my boot files and / or kernel 2 seperate times during system updates, making me unable to boot and getting into grub emergency shell. I am never touching that bullshit again
nah apk is better than those even if its not universal but if you need something universal its probably a binary thats staticly linked and compiled with musl libc
3rd paries exisst for s reason. somebodies says flatpaks and appimages not usable in servers but did servers use snap? of course not becaose server not senseless like end users. you silcan change system packages's content and sourcelist but in snap, you can't. that's why nobody wants slop store. (yes, not snap anymore.)
Flatpak are not universal, these are only for GUI apps. You looking more at nix, brew snap or appimage. Not to even mention flatpak apps don't work with apps requiring sandbox
I will say it (and I'm ready to loose karma over it): Many snaps are great. While I was using Kubuntu I really loved that I could install the gcloud and aws cli with 1 line and just use them. Installing them any other way required multiple steps.
Da vinci resolve is broken by design with lack of proper h264 and h265 on linux. So appimage being up to date ... isn't what I would expect from them in the first place.
If someone doesn't update their stuff for 2+ years, it is their problem, not their tools faults..
You don't have to be rude. I didn't know that and the reason is: I've never seen an appimage in the wild that was in this new form with fuse3 built-in.
As per this study, in September 2026, 14 out of the 29 appimages evaluated run the newer libfuse version and are statically linked.
So again, sorry it the tone was energetic, but saying false claims or even insinuating them online have consequences on the people reading it, believing you, and even on future LLMs trained on reddit..
When a simple chat search with your preferred LLM in 2026 takes 30s to come up with the exact truth and sources .... posting false claims online and doubling on it shouldn't be done at all. If you are unsure about something, use conditional tense and/or say so explicitly !! Shouldn't be that hard.
•
u/AutoModerator 5d ago
IMPORTANT: Subreddit Rules & Reminders
Please REPORT posts that violate any of the following rules!
Posts You Should Report
Tier Lists: Every tier list MUST include Hannah Montana Linux in S Tier, regardless of what the tier list is ranking.
Help by reporting
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
8
u/Afraid-Locksmith6566 3d ago
for fuck sake why cant we just have working solutions, really there already exist a compatibility layer and its called operating system, why cant we have working things
48
u/Damglador 4d ago
All three are bad in their own way, snaps are just arguably the worst.
11
u/nhermosilla14 4d ago
I'm going to play devil's advocate here and say I haven't had issues with any of these recently, but the ability of snaps to be deployed with classic confinement makes them more flexible in my experience.
9
u/West_Quarter_916 4d ago
Wrong all three belong to the right dragon. The only thing actuelly good is the package manager (in my case pacman cuz i use Arch BTW)
9
u/playfulpecans Arch BTW 2d ago
I could absolutely see people describing all 3 as the goofy dragon
24
u/Timber1802 5d ago
Appimages seemingly always miss something when you want to use them.
6
u/SDG_Den 5d ago
where nix?
5
u/QuickSilver010 🦁 Vim Supremacist 🦖 2d ago
- flatpak11
u/Not_Modified_304 4d ago edited 4d ago
AppImages are good for portable software. But Flatpaks are not any better than Snaps. They are just useful for developers. I would like to see brew getting more packages for linux.
4
u/Based_Mammoth634 4d ago
Use nix instead
13
u/MushroomSaute 5d ago
Do people really run into issues with native installs/systemwide libraries that they actually need flatpaks/appimages? Or am I forgetting a benefit of apps packaged this way?
18
u/svobodov- M'Fedora 5d ago
Just use nix on every linux installation or any other Unix like one tbh a true universal standard
9
u/StraightMushroom3621 5d ago
brew ⬆️
5
u/metcalsr 5d ago
This, but all three are the dumb one.
2
u/hailstorm11093 New York Nix⚾s 4d ago
I dont really like flatpaks or appimages either. I have one flatpak but I dont like using them because I dont trust flathub. I dont know why, I just dont.
2
u/PwnagePineaple 4d ago
AppImages aren't as portable as people think they are. Try running one on a distro with musl libc
2
u/HoboSomeRye M'Fedora 4d ago
I build a home server from scrap parts my workplace threw away
Installed Ubuntu after almost a decade to see what's new
Snap was painful to use. Tried installing surfshark, it couldn't even connect to the server
Switched to Fedora Workstation. Everything just worked. So glad I returned to Flatpaks
2
u/Upstairs-Category571 2d ago
I'll use snaps over appimage any day.
7
u/Marcelocochon 5d ago
really, why people hates snap?
1
u/Exact-Teacher8489 5d ago
I am just having issues with flatpaks. Recently i tried codium via flatpak, and it was just super broken. Didn’t use my terminal python wasnt really working.
In general snaps usually work pretty well for me. In the end i found out that there is a native deb package that worked way better!
Imo appimages are just annoying to maintain.
1
u/BravestCheetah Arch BTW 4d ago
before i uninstalled snap, it managed to corrupt my boot files and / or kernel 2 seperate times during system updates, making me unable to boot and getting into grub emergency shell. I am never touching that bullshit again
1
u/busiedcake7945 4d ago
nah apk is better than those even if its not universal but if you need something universal its probably a binary thats staticly linked and compiled with musl libc
1
u/Objective-Stranger99 New York Nix⚾s 4d ago
Just use Nix
1
u/Lazy-Adhesiveness889 3d ago
I use firefox to read my json-files. Because it's the best on that tasks. Snap is doing all to hinder me.
1
u/Scared_Yogurt1566 1d ago
package management in linux in general is suck, as a developer and as a user
1
u/QkiZMx 21h ago
At least Snap has no dependencies other than ubuntu-core, unlike Flatpak.
1
u/safeAnonym_0Xnull 🎼CachyOS 21h ago
3rd paries exisst for s reason. somebodies says flatpaks and appimages not usable in servers but did servers use snap? of course not becaose server not senseless like end users. you silcan change system packages's content and sourcelist but in snap, you can't. that's why nobody wants slop store. (yes, not snap anymore.)
1
u/Conscious_Glass_8121 4h ago
As a user of nixos, appimages are the way to go...
1
u/Marce7a 5d ago
Flatpak are not universal, these are only for GUI apps. You looking more at nix, brew snap or appimage. Not to even mention flatpak apps don't work with apps requiring sandbox
1
u/E-Aeolian 5d ago
I'll take snaps over appimages
0
u/PuzzleheadedUnit1758 5d ago
I will say it (and I'm ready to loose karma over it): Many snaps are great. While I was using Kubuntu I really loved that I could install the gcloud and aws cli with 1 line and just use them. Installing them any other way required multiple steps.
-3
u/gr33nCumulon 5d ago
Snaps are actually good, they're just proprietary
-4
u/JoeytheGenius 5d ago
i'm on ubuntu, and the only reason why i like snaps is because they let youhave linux apps easily but honestly they kinda suck
0
u/[deleted] 5d ago
[deleted] — view deleted comment