don't care still using appimages and not flatpaks
Thats a very constructive point!
By the way, if you guys are interested here is a talk comparing Appimages Snaps and Flatpaks by Richard Brown, one the devs at Suse, a big contributer to openSuse and the guy who spearheaded the Desktop variante of MicroOS (the immutable openSuse Tumbleweed).
He isn't to keen on appimages either because of a miriad of technical issues.
youtube.com/watch?v=4WuYGcs0t6I&t=456
For all the Grayjay/Newpipe/Freetube users
Very good video with additional points, will add them
Why do I hear the argument about no .desktop entries in every thread like this? Creating a .desktop file is a requirement for the appimage creation tools to work, and appimaged installs it in the system menu immediately. It's seamless.
flatpak?
Frying pan, meet fire.
AppImages as a universal packaging format seem fun in that I've had loads of issues getting them to run properly on different systems. I'm sure they're handy for some stuff but haven't personally enjoyed them.
AppImages can be signed. Flat pak is the lesser option for security
Explained in a other comment how a pain it is to verify such a signature.
Is that stored in the appimage file?
I find it funny how flatpak neglectors always spell it wrong
I don't use app images of flatpaks. I don't like either.
I hate them both, give me a .Deb (or equivalent) if you're gonna package it. And get off my lawn! 🤣
Installing .deb files from random sources is also very insecure and not reliable for updates.
It would be nice if there was a way to bundle up a flatpak that was at risk of disappearing
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.
Linux
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