Needed to have zulip to talk about a bug, the AUR package was a pain to debug, the appimage in ~/.local/bin just works™.
this post was submitted on 04 Mar 2024
220 points (81.2% liked)
Linux
48376 readers
1701 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I don't use app images of flatpaks. I don't like either.
Feather Wallet is a great example of AppImages done right
I hate them both, give me a .Deb (or equivalent) if you're gonna package it. And get off my lawn! 🤣
load more comments
(6 replies)
Flatpak is bloated monster that has no idea how much it has to download to update. I'll take AppImage over flatpak if I can.
Flatpak has a good package manager?
Read the other comments etc. No motivation to repeat everything
load more comments
(5 replies)
Static binaries, or dynamic binaries whose project has documentation on what dependencies they need, are better than appimages. This is because appimages are a container with the actual files inside, creating a layer of abstraction, and appimages require libfuse to work.
Imagine the case in NixOS, where dynamically-linked binaries don't work out of the box. You can patch or package these binaries, or just quickly use something like steam-run to emulate traditional Linux bin and lib paths, it works. With appimages, it won't work unless you already have libfuse in your system, so you have to extract the appimage first.
Still, flatpaks as the only official alternative isn't great for many reasons, and CLI/TUI programs are out of the equation. What is better is the devs distributing unpackaged binaries, jars, etc, and optionally flatpaks. Either way, Nix's repository is huge so I don't usually feel the need to run anything that isn't a nix package.