Snap bad
Snap bad
Snap bad
Hadn't snap fixed a lot of the complaints people initially had?
Has it? My complaints are: I have to use VPN software for work that replaces /etc/resolve.conf with a symlink to another location, one that sandboxed snaps can't access. There's no way to grant them access; the "slots" that you can connect are fixed and pre-defined. You can't even configure the file path; it's defined right in the source code. Not even as a #define, but the string literal "/etc/resolve.conf". That seems like poor practice, but I guess they're not going for portability.
Also, I have /usr and /var on different media, chosen for suitability of purpose, and sized appropriately. Then, along comes snap, violating the File Hierarchy Standard by filling up /var with application software.
Minor annoyances are the ~/snap folder, and all of the mounted loopback filesystems which make reading the mtab difficult.
Probably, but the stink will linger for quite a long time.
There's a burger place near my house that I use to go to almost every week. But then the quality started going down, and I stopped going there. That was two years ago. Maybe they fixed the problems, but I'm not going to know - because I no longer go there. Snap is like that.
I think the main complaint is that it seems like Canonical is trying take control of Linux packaging. Don't they handle their stuff in a way that pretty much prevents third party 'Snap Stores'? Like, their backend being closed source and their software only accepting their own signatures?
laughs in Nix and NixOS
Like a bunch of old farts in a coffee shop arguing over which truck brand is better.
Yeah, but Snap is the equivalent of Tesla...
You want me to top off your coffee before you go home to take a nap?
If flatpak didn't make me put the entirety of KDE onto my system (thats an exaggeration but you know what I mean) I'd gladly crown it king of the package managers.
I just want to point out the dependencies of Konsole (arguably a small and simple application in concept): glibc gcc-libs icu kbookmarks kcolorscheme kconfig kconfigwidgets kcoreaddons kcrash kdbusaddons kglobalaccel kguiaddons ki18n kiconthemes kio knewstuff knotifications knotifyconfig kparts kpty kservice ktextwidgets kwidgetsaddons kwindowsystem kxmlgui qt6-5compat qt6-base qt6-multimedia sh
.
Plus make it hell on earth to a) access drives other than the one flatpak is installed on, b) interoperate with non-flatpak applications, and c) retain any amount of free space on my drives (exaggeration for effect).
Psst .. the first KDE app you installed via your package manager also put "the entirety of KDE" onto your system.
Are there enough watermarks on this meme? At least we got reddit covered.
makes it authentic lol
A rusty bucket riddled with holes and the stick part of a shovel is better than snap for running software.
A magnetised needle and a steady hand is a better package format.
A stab at my personal ranking: .deb > appimage > flatpack > curling a shell script
I can't help but love a .deb file (even when not via repo), I've almost exclusively used Debian and it derivatives since the late 90s. And snap isn't on the list because it got stored in a loopback device I removed.
Am I the only one who struggled extensively with .deb file with out-of-date dependencies? It seems the software dev needs to update the .deb file frequently, which they never do.
xbps > pacman > apt imo
I just recently de-snapped yet another ubuntu system. Couldn't agree more. I use debian standard for all of my stuff, and I agree with your ranking.
As someone who is confused when he has to deal with a .deb file and always has to google what to do with it - what is the advantage of a .deb over let's say a shell script?
It might be different for other distros, but for me on MX Linux, I just click on the .deb and it opens a shell with a root prompt and installs the file automatically. Easy peasy.
If made correctly (which is hilariously easy), it's a clean install and uninstall process, support some level of potential conflict regarding files that are shared with other packages/commands, support dependencies out of the box, and with minimal work can be made easy to update for the user (even automatically updates, depending on the user's choices) by having an (again, very easy to setup for a dev) repository. With the added value of authenticity checks before updating.
All this in a standardized way that requires no tinkering, compatibility stuff, etc, because all these checks are built-in.
Note that some of this probably applies to other system package management solutions, it's not exclusive to .deb.
Well for one a .deb comes out of the box with an uninstall machenism. As well as file hashes, package singing, etc...
dpkg -i <nameofpackage.deb>
Which can be read as: (Debpackage) -install <nameofpackage.deb>
That's it!
Also, if you haven't already, install tldr (apt install tldr), then you can 'tldr deb' (or any other command) to get a few examples of their most used functions.
I never fully trust a shell script and usually end up reading any I have to use first, so I know what they do. And after so many years dpkg holds no mysteries for me and Discover will install .debs if I double click while in KDE.
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.
If it's not in Apt, I just run it in docker.
Why the hate part of AppImage?
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.
For me it is the "Windowsy" feeling of downloading an executable from some website. I prefer having all my packages managed in one place.
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.
Missing dependencies. (Or wrong version of fuse)
No automated updates has be the biggest reason for me.
my issue with snaps is honestly just that they are controlled too much by just one entity (canonical) and there is no reason for them to exist because flatpak already does everything they do.
Yup, thats why a tarball is better
I tried a snap package on my pop-os system once & it poo'ed folders all over my system, then didn't actually uninstall when I uninstalled it.
No thank you.
thats the thing with snaps: they go all over the place on your system, so even if you uninstall it (which itself is a tiring and cumbersome task at times!), they magically stay everywhere on the systems, with tons of folders and files.
I have really started to like AppImage. You just download a single file make it executable and it just works.
I use Cursor for coding, and it has an appimage that replaces itself when it updates.
Some apps are a bitch and a half for some reason, other apps just work
Make a .desktop file, slap it in ./local/share/imdrawingafuckingblank and boom, it's integrated into your shell menu like any other app
The Nexus Mod App and Foundry VTT work flawlessly and it's so nice
Why tf does every app have to mount itself as a virtual block device?
This annoys me when I don't have a command aliased to filter them.
Because fuck you, that's why
Only tangentially related - but a friend brought over a new kubuntu install and Canonical had the cheek to demand money for VLC patches? They don't fing own VLC. What the actual f is going on over there, Canonical?
Mark Shuttleworth is a greedy bastard and it’s finally starting to show.
Eh. He's done more for Linux than you, I, or anyone else in this thread for that matter.
Is it backports for an old version?
I don't know, this was for a system on kubuntu 24.04, the latest up there. I removed it, replaced it with debian and kde - my friend isn't a gamer, doesn't require anything bleeding edge, so that was just a better choice in our opinion.
I really like flatpak and it's system, but AppImages are in a nice second place. I usually look for a flatpak first and appimages if I can't find the first.
Don't worry, Snap: Flatpak and Tarballs are NOT better by much. And, chances are, the system package manager may be lacking in so many validation requirements that it's not iso27002-compliant and thus could be junk.
There-there, Snap. Most people won't even know why you suck.
.tar.gz should be appimage.
I'd love to use flatpak more, but with my peculiar internet situation, installing a single package can take 6-7 hours.
i just got an Ubuntu machine at work, and really simple packages are only available as snaps. so i guess i’m going to try out Nix home-manager
Apt is kind of broken, to be honest. No package should have full system access during installs or execution.
Fuck flatpak, all my homies hate flatpak
🎩
./configure; make; sudo make install;
🎩
wget -q -O- https://raw.githubusercontent.ru/linux-security/security.sh | sudo bash
It's sucks I really don't like make install and script would randomly mess app root file system I would be happy if package manager would control it
Appimage>your inferior packaged application method