A magnetised needle and a steady hand is a better package format.
Seeing “.TAR.GZ” in all caps gives me strong feelings of wrongness.
Unfortunately imgflip prints text in all caps only.
Yes, the format demands it; no fault implied on your part, just commenting on how it hits
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.
Nix is just across the street sipping tea because it understands what it is and is at peace with the chaotic world around it.
I use NixOS and Flatpak (Nix-Flatpak) to install software that is not available in Nixpkgs. Unlike Arch’s AUR, Nixpkgs has fewer popular packages. However, Nixpkgs beats AUR in terms of quantity because many Nixpkgs packages are redundant.
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.
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?
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.
Well for one a .deb comes out of the box with an uninstall machenism. As well as file hashes, package singing, etc…
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.
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.
Psst … the first KDE app you installed via your package manager also put “the entirety of KDE” onto your system.
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).
This is a “security” feature and I’m so tired of it. Same thing with Wayland, random crap doesn’t work sometimes
Wayland is trying to replace a standard that people have been saying is obsolete for a decade. I’ll give them a bit of leeway.
deleted by creator
That’s because we are…
If .y Firefox will once again be updated without asking me and then refusing to open any page without a restart I’ll fucking lose it
Wait hold on wait, does that bullshit have something with Firefox being distributed through Snap?
If it does, I’m going to sn… also fucking lose it
Yeah, it’s snap
Always updating without letting you know, without asking and it’s ALWAYS at the most inconvenient time
Ah gotcha, it’s not the cause but it makes the problem way worse
It basically IS the cause as it’s the system doing the updates without asking. But snap has other issues too. For one, it’s the slowest installer in recorded human history, it takes literally ten times longer on snap to install anything. Why? Beats me, in theory it ought to be faster as it shouldn’t have to resolve dependencies but here we are. Try installing anything with snap, it takes forever.
Then, snap is closed source eon the server side, so fuck all of that, that’s already 200% of reasons not to use it ever. I don’t trust closed source software anymore
By “problem” I meant having to close Firefox before further browsing, not automated updates - I don’t know if I could stand daily-driving a system with Snap updating my stuff while I’m trying to use it tbh, that’s one of the main reasons I left Windows behind.
Your first comment gave me the impression that Firefox required a restart because it’s distributed officially through Snaps or something, idk 27 days have passed since then
The required FF restart after updating is indeed an FF thing, but in combination with snap just updating without asking is extremely annoying.
Having used Windows quite a few times in my life, I know the feeling
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.
That’s cool and all but it would be even cooler if you could just install and keep it updated through your package manager
Some AppImages have that built in, like Ente.
That’s kind of the point though. One of the foundational pillars of a good distribution is mature package management, and that includes not relying on self-updaters that will pollute your system with untracked files
I use AM package manager for that.
That’s cool.
It would still be even cooler if the app makers just packaged them for distros. Or even just Flatpak.
But that’s a cool project I’ll keep it in mind for my next go with an immutable distro
Or even just Flatpak.
AM was started because flatpak sucks.
-
With flatpak devs can’t agree to use a common runtime, so the user ends up with a bunch of different runtimes and even EOL versions of the same runtime, making the storage usage 5x more than the appimage equivalent and this is much worse if you use nvidia which flatpak will download the entire nvidia driver again.
-
flatpak could not bother to fix the hardcoded
~/.vardirectory, something that AM fixes by simply bind mounting the existing application config/data files to their respective places when sandboxing which yes it is able to sandbox appimages with aisap (bubblewrap). -
flatpak threw the mess of handling conflicting applications to the user, so you have to type nonsense like
flatpak run io.github.ungoogled_software.ungoogled_chromium, AM just puts the app toPATHlike everyone else does, even snap doesn’t have this issue.
-
Why tf does every app have to mount itself as a virtual block device?
Serious question: why not? What’s bad about that?
Because with snap
lsblkgets very cluttered, making it hard(er) to find any disk you’re looking for.Edit:
lsblkor any other command that lets you see all the connected disks really
