Linux

48323 readers

919 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

214

Don't use Appimages (a writeup about all the reasons they are a pain for users) (github.com)

submitted 8 months ago by Pantherina@feddit.de to c/linux@lemmy.ml

180 comments fedilink hide all child comments

Appimages totally suck, because many developers think they were a real packaging format and support them exclusively.

Their use case is tiny, and in 99% of cases Flatpak is just better.

I could not find a single post or article about all the problems they have, so I wrote this.

This is not about shaming open source contributors. But Appimages are obviously broken, pretty badly maintained, while organizations/companies like Balena, Nextcloud etc. don't seem to get that.

you are viewing a single comment's thread
view the rest of the comments

[–] TheAnonymouseJoker@lemmy.ml 7 points 8 months ago* (last edited 8 months ago) (4 children)

I do not agree. AppImages can be double clicked and executed. They are not a pain to use. I have a few dozen AppImages besides a few Flatpaks and plenty native packages on Debian. Comfortable setup that carried over from Ubuntu LTS.

This poster advertises GrapheneOS propaganda, and I never take those security weirdos seriously anyway, so either way I do not consider their security arguments as valid. All of these people have a common theme – pushing people towards becoming dependent on them, their "repositories" and apps, forming cults around it and becoming self-approved security gurus and dishing out moronic advice.

If there was a way for these people to be able to rebrand one of the non-native packaging formats, they would shill the fuck out of it, just like GrapheneOS.

[–] yukijoou@lemmy.blahaj.zone 5 points 8 months ago (3 children)

AppImages can be double clicked and executed. They are not a pain to use.

i can understand that, but flatpaks are easier to upgrade and automatically integrated into your package manager, which (i believe) isn't as straight forward for appimages. also there's one major repo where you can find most apps (flathub) making app-hunting less daunting i feel like.
also, once your app is installed, it's always in your system menu, so that doesn't change much in the long run

Comfortable setup that carried over from Ubuntu LTS.

can't you carry over flatpaks as well? you can probably copy /var/lib/flatpak or wherever they store their stuff from one system to another, or failing that, save all the app IDs you have installed, and re-install them onto your new system, backing up ~/.var to keep all your data!

[–] sxan@midwest.social 1 points 8 months ago (1 children)

Flatpack puts all app data in ~/.var?? Ewww! No thanks.

[–] yukijoou@lemmy.blahaj.zone 1 points 8 months ago

not sure about the path, you should check flatpak's docs for more accurate informations

but i believe so, yeah

on one had it's a shame they're not using xdg dirs, but on the other, i kinda get why -- it's neither config files, nor just data -- it's both, it's a container

load more comments (1 replies)