this post was submitted on 11 Jul 2023
205 points (91.8% liked)

Linux

48186 readers
1638 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

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
205
Anyone else starting to favor Flatpak over native packages? (lemmy.one)
submitted 1 year ago by DidacticDumbass@lemmy.one to c/linux@lemmy.ml
266 comments fedilink hide all child comments
 

I am currently using Linux Mint (after a long stint of using MX Linux) after learning it handles Nvidia graphics cards flawlessly, which I am grateful for. Whatever grief I have given Ubuntu in the past, I take it back because when they make something work, it is solid.

Anyways, like most distros these days, Flatpaks show up alongside native packages in the package manager / app store. I used to have a bias towards getting the natively packed version, but these days, I am choosing Flatpaks, precisely because I know they will be the latest version.

This includes Blender, Cura, Prusaslicer, and just now QBittorrent. I know this is probably dumb, but I choose the version based on which has the nicer icon.

you are viewing a single comment's thread
view the rest of the comments
[–] KindaABigDyl@programming.dev 5 points 1 year ago

You have outdated information. There are no longer any tradeoffs to AppImages:

  1. Yes there is no "official" default installation path, but like how XDG_DATA_PATH isn't technically a standard but practically it is, the de-facto standard is ~/Applications now, and most AppImage-based tools respect that.
  2. They integrate fine with the system. Better than Flatpack and Snap, actually. I've had lots of issues with flatpaks not respecting themes, but never AppImages. Not sure where you got that from.
  3. I solved the other problem with AppImages with a package manager I wrote. Centralized location pointing to AppImage urls, and it downloads and keeps them updated. And no, you don't need to write your own, there are multiple AppImage package managers out there.

On the flip side, there's no weird extra locations like how flatpak installs apps, you know exactly where the program is in case you want to launch it manually, you can mix apps available in your package manager with ones you download directly seamlessly, no dependency hell or version problems as AppImages are self contained (even multiple versions at the same time), etc, etc, etc all the benefits people spout about AppImages.

AppImages imo are the superior cross-platform package format as there are no tradeoffs and no downsides, meanwhile:

  • Snaps are slow and proprietary
  • Flatpaks suck to create and maintainers select all on sanboxing, so it's a complicated mess for no reason, and they also have bad theming that never works half the time.