One of the reasons Pop!OS was so nice was the introduction of these to me. Changed my life cya windows
I personally, prefer nix
You must run
curl http://totallylegitwebsite.ru/install | sudo sh, it’s the only way to install our product. Don’t even look at the several thousand lines of illegible shell script, just pipe it straight to your shell. We are a very serious project.I hate this model, but if you trust the website, piping to shell is exactly as safe as downloading and executing a installer. (Yeah yeah, https, function executed on last line, etc)
I don’t want to trust a website, which is susceptible to typos and lookalikes (see e.g. putty.org) and relies on countless other services that can inject malware.
Code signing was creates for this reason: ensure that the program is authentic and unaltered. Package managers do this perfectly.
Fun fact: you can just install the precompiled binary on Linux, but thanks to some nerds in the Linux community, that’s usually unavailable, because “you must compile it yourself, it’s easy”, except the software requires you exact versions of build tools and compilers, otherwise it’ll fail to build, because realshitmake 2.5.0.8 dropped support for a 2.1.5.6 feature.
“why people doesnt want to use my favorite obscure linux distro? 😔”
Appimages use the deprecated fuse2 dependency, never integrate well on the system, and run unsandboxed. I personally hate them.
appimage hasn’t depended on libfuse2 (or any libfuse) since the static runtime came out in 2022.
The issue is that some projects haven’t updated to it, most notably electron builder:
https://github.com/electron-userland/electron-builder/issues/8686
never integrate well on the system, and run unsandboxed.
You have sandboxing and perfect integration, including adding the binary to
PATH.Thanks for this comment. I’ve been struggling with this and the “out-of-the-box functionality” of the .appimage’s
I don’t think you made this post correctly, it shows the image in the body text and not like other posts
other example
I think I fixed it; I use Jerboa and put the image link in the wrong field. Whoops!
looks fixed on my end too!
also a funny coincidence but I got a notification “I think I fixed it; I use Jerboa and…” which is funny because I was talking about fingernail issues with someone else and Jojoba oil is something used for nail care so I thought it was them replying lol
I find different formats good for different purposes. Apps I use frequently are flatpak, single use apps are appimage, and apps that need more privileges gets to be system packages.
In general I agree, I love me some appimage, but Flatpak is good when you need sandboxes and repo packages are super easy with apt or dnf
but Flatpak is good when you need sandboxes
flatpak sandbox is actually bad for web-browsers and electron apps:
https://librewolf.net/installation/linux/#security
https://seirdy.one/notes/2022/06/12/flatpak-and-web-browsers/
https://github.com/uazo/cromite/issues/1053#issuecomment-2191794660
i use nix btw :3
I don’t understand how literally every way of installing a program on Linux is controversial or incredibly confusing
Windows is just .exe possibly a couple clicks that’s it. possibly it’s a .msi which is also super easy. 99.5% of the time no issues whatsoever.
however in Linux there are 27 different ways and none of them work well, so anytime you try to install something to do something incredibly basic it’s like “enter these 5 terminal commands you have no idea about” or it just gives you a file with no instructions on what the hell to do with it.
then there’s OSes that don’t even support installing things for some reason???
and whenever you DO manage to get it to run after 2 hours of googling whatever the fuck a program.rpm file is it doesn’t even work!!
maybe I’m just really dumb but how the hell can this be such a simple action in a computer and be so incredibly complicated??
which one out of 50 are the one I’m looking for? NO IDEA!!
Forget everything anyone told you about Linux, think of each distro as its own OS.
Flatpak and Snap are the ones that work with everything and are the closest equivalents to .exe files. App images are kinda like the portable apps that were popular like 10-15years ago on windows. (Anyone remember using portable Firefox on a flashdrive?)
In addition to these each distro has its own kind of package format. (.DEB, .APK, .RPM, etc)
Just because 2 distros share a package format doesn’t mean they are compatible, in the same way a winxp .exe might not work on win11.
Idk if windows still has a 32bit version, or if it has an ARM version, but that’s what the .amd64 and .arm64 thing is for. Most people want .amd64.
Except for the .RPM package (which is presumably a Fedora package) all of these are clearly labeled by distro (Debian 10, Debian 11, Ubuntu, etc).
If you have a 64bit CPU and run Debian 11, you want:
debian-11-amd64.deb
but why run this over flatpak,snap,or appimage?
Disk space. System packages like this do not bundle the dependencies to run the application with it. Instead the dependencies are installed on the system a single time and shared between all applications.
Nowadays there is a push to migrate to using things like flatpak and snap but some old school Linux heads don’t really want to for either political reasons or just because it’s different than what they are used to.
Not sure why they have multiple debs and RPMs when meta package dependencies can solve that.
Otherwise?
It’s because Windows only has an x86_64/amd64 CPU architecture.
Here there’s ones for multiple ARM CPU architectures going back to the first raspberry pi.
If Windows was readily available for those you can bet it’d be just as confusing with “wait am I armv6 or armhf? Or oh shit am I armv7??”
Arch is pretty nice because like 95% of things you would want to install are either in the official packages or on the AUR. And either way is very simple to do, you just look up “____ package Arch”, see what it’s called, and then run
sudo pacman -S ____oryay ____It’s fundamentally the difference between Linux’s modular design and Windows’ monolithic design at play.
Because Windows is closed-source and all OS copies are something which only Microsoft can create, and because Microsoft only officiated the .exe filetype, that’s all you’ve got as an option (this is technically not the only type, though, since you have Python and Java executables as options as well).
Meanwhile Linux is opensource and relies on the opensource community to add more convenient systems and interfaces. Different design philosophies clash in that space, and OS’s additionally try to carve out influence by making exclusive systems, like package management softwares. This creates the splintered environment we see now. It’s essentially just politics which does not exist in the more dictatorial design (as in the design is dictated by a very small group within Microsoft) of Windows.
yay flameshot
Don’t forget avout ease to move across devices!
What’s wrong with Flatpak?
With flatpak I feel like I’m installing a new entire enviroment for every app I’m installing
It only installs dependencies once. If you install 10 libadwaita apps or 10 KDE apps, you only get 1 copy of libadwaita or KDE framework.
flatpak still ends up using +4x times the storage equivalent of appimage, comparison with flatpak dedup checker for ~20 common GUI apps:
And btw I need to update this comparison, a lot of the appimages on the right got a lot smaller lately.
The flatpak runtimes are huge, the GNOME runtime alone is over 2 GiB so that’s +20 appimages.
I feel like the morpheus neooooo meme would also be a good fit, I’m cracking myself up thinking about it
