this post was submitted on 11 Jul 2023
164 points (92.7% liked)

Linux

48031 readers
770 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
nooter692@lemmy.ml
AgreeableLandscape@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
164
Anyone else starting to favor Flatpak over native packages? (lemmy.one)
submitted 1 year ago by DidacticDumbass@lemmy.one to c/linux@lemmy.ml
229 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
[–] Daeraxa@lemmy.ml 6 points 1 year ago (3 children)

Nope, don't like them. Nor snaps. I find the sandbox nature annoying and many developers don't actually seem to understand it correctly anyway meaning you have to use flatseal etc. Then having to deal with some apps writing config within the sandbox and some writing it outside the sandbox...

My order of preference is generally I pick the "official" supported version as opposed to any community maintained ones. Then within that:

  • Install via the language's package manager (cargo, npm, pipx, cabal etc.)
  • Appimage
  • Native package (.deb, .rpm etc.)
  • Plain binary
  • Build from source
  • Snap
  • Flatpak
[–] DidacticDumbass@lemmy.one 2 points 1 year ago

True. I have run into a lot of dumb issues with sandboxing, mostly in choosing a folder other than downloads for file interaction.

I have overlooked Appimage, and I will consider it. I am intrigued that you put it before native package. I had not considered using the package manager of the language it is built in, which honestly is probably the optimal way to install a package.

Alright, I have some reading to do. I love learning new ways to do things. I am glad I asked!

[–] StudioLE@programming.dev 2 points 1 year ago (1 children)

Out of interest why do you favour snap over flatpak?

[–] Daeraxa@lemmy.ml 2 points 1 year ago

I've just had fewer issues with snaps. Honestly I don't care for either of them so the difference between them for me is pretty slim but I just find Flatpak to be particularly annoying, Snaps just haven't caused me any real issues other than polluting my device list with endless loop devices.

[–] tony@lemmy.hoyle.me.uk 1 points 1 year ago

I handle it by spinning up an lxd container to try new apps.. then they have the whole machine to do what they like, and if the install doesn't work or I hate the app, just delete the entire container.

lemmy was one of the harder ones to deal with because it needs docker.. I have a special profile that runs docker in a container for apps like that (I never run docker bare, it f..s around with the firewalling and breaks stuff).