this post was submitted on 07 Jul 2025
699 points (93.0% liked)

Linux

56365 readers
570 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 6 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] kaidezee@lemmy.ml 6 points 2 days ago

Don't like it for one simple reason: no integration with the distribution. Flatpak is this sort universal solution that works, but doesn't necessarily work hand-in-hand with the distro, unlike package managers.

[–] MoondropLight@thelemmy.club 26 points 6 days ago (1 children)

Perhaps ironically, this is mocking a strawman. Flatpacks can be installed and managed using the terminal! Not only that but Linux-Distros have had graphical package managers for decades.

The primary reason that distros have embraced flatpack / snap / appimage is that they promise to lower the burden of managing software repositories. The primary reason that some users are mad is that these often don't provide a good experience:

  • they are often slower to install/start/run
  • they have trouble integrating with the rest of the system (ignoring gtk/qt themes for example)
  • they take a lot more space and bandwidth

Theoretically they are also more secure... But reality of that has also been questioned. Fine grained permissions are nice, but bundling libraries makes it hard to know what outdated libraries are running on the systems.

load more comments (1 replies)
[–] Limonene@lemmy.world 42 points 6 days ago (5 children)

I've never heard anyone say that Flatpaks could result in losing access to the terminal.

My only problem with Flatpaks are the lack of digital signature, neither from the repository nor the uploader. Other major package managers do use digital signatures, and Flatpaks should too.

[–] Obin@feddit.org 10 points 6 days ago* (last edited 6 days ago)

Nah, it's the same as with systemd, docker, immutable distros etc. Some people just don't appreciate the added complexity for features they don't need/use and prefer to opt out. Then the advocates come, take not using their favorite software as a personal insult and make up straw-men to ridicule and argue against. Then the less enlightened of those opting out will get defensive and let themselves get dragged into the argument. 90% that's the way these flame wars get started and not the other way around.

For the record, I use flatpak on all my desktops, it's great, and all of the other mentioned things in some capacity, but I get why someone might want to not use them. Let's not make software choice a tribalism thing please. Love thy neighbor as thyself, unless they use Windows, in which case, kill the bastard. /s

load more comments (4 replies)
[–] beyond@linkage.ds8.zone 12 points 5 days ago (1 children)

Not a fan for a few reasons. Flathub (as far as I know) works on the app store model where developers offer their own builds to users, which is probably appealing to people coming from the Windows world who view distros as unnecessary middlemen, but in the GNU/Linux world the distro serves an important role as a sort of union of users; they make sure the software works in the distro environment, resolve breakages, and remove any anti-features placed in there by the upstream developers.

The sandboxing is annoying too, but understandable.

Despite this I will resort to a flatpak if I'm too lazy to figure out how to package something myself.

[–] scholar@lemmy.world 3 points 4 days ago

The sandboxing is part of the point, having a permissions model that puts the user in control of what programs are allowed to do is critical.

[–] muusemuuse@sh.itjust.works 9 points 5 days ago* (last edited 5 days ago) (2 children)

Enter the calm and quiet room

Pass out torches and pitchforks, guns and knives

“Snaps exist”

War erupts.

[–] sudo@programming.dev 8 points 5 days ago
[–] grue@lemmy.world 4 points 5 days ago (1 children)

War with who? I'm posting this from Kubuntu and I'd happily agree with you that Snap should fuck off and die. (In particular, the backend being controlled by Canonical makes it objectively bad compared to Flatpak.) Even among people like me who tolerate Snap (for now...), I really don't think you're gonna find anybody who actually likes it, let alone enough to champion it.

Can't start a war when there's a consensus!

[–] Decker108@lemmy.ml 1 points 4 days ago

Oh, hi! I also use Kubuntu, but I love Snaps! I use them for everything. I even tried to use a Snap-version of the kernel, but it completely destroyed my system so I had to reinstall... but other than that, they're great.

[–] bunitor@lemmy.eco.br 15 points 6 days ago (1 children)

flatpaks are fine and useful, i just wish we didn't move into a scenario where applications that used to be easily available in distro repos start moving away from them and are only available through flatpaks. distro packages are just so much more efficient in every way. flatpaks are easier on maintainers and developers but that comes at a cost to the user. i have about a dozen or less flatpak apps installed and already i have to download at least 2 gigs of updates each week. i run debian

load more comments (1 replies)
[–] limelight79@lemmy.world 7 points 5 days ago

I "grew up" with Slackware, so I definitely understand the dependency issue.

I like flatpaks (and similar) for certain "atomic" pieces of software, like makemkv. For more "basic" software, like, say, KDE, I want it installed natively.

[–] rumba@lemmy.zip 7 points 5 days ago (1 children)

I need OBS on this new computer!

Let's install the flatpack!

V4l problems

Plugins Problems

Wayland Problems

I'm just going back to the .deb, thanks.

[–] csolisr@hub.azkware.net 10 points 5 days ago

Flatpak being securely sandboxed by default is both its biggest strength and its worst point of contention. The XDG is still scrambling to replicate the permission requests paradigm from Android on the Linux desktop.

[–] Crabhands@lemmy.ml 12 points 6 days ago

I'm 2 months into my Linux journey and I don't use flatpak. I've had the odd problem with it. I stick to pacman and yay now.

[–] spookedintownsville@lemmy.world 10 points 6 days ago (3 children)

The issue I have with flatpaks is the size for most applications. It just doesn't make sense for me. Not that it's not useful and has it's purposes.

[–] isVeryLoud@lemmy.ca 6 points 6 days ago (1 children)

Flatpaks aim to be a middle ground between dependency hell and "let's pull in the universe" bloat.

Applications packaged as Flatpaks can reference runtimes to share "bases" with other applications, and then provide their own libraries if they need anything bespoke on top of that.

[–] MangoCats@feddit.it 8 points 6 days ago* (last edited 6 days ago) (5 children)

And they are still, in my experience, slow to load, a cumbersome addition to the update process, and often un-necessary.

Don't get me wrong, if you're in a tight spot and can't make two significant software packages work in a distribution due to conflicting library version requirements... some kind of lightweight container solution is attractive, expedient, and better than just not supporting one of the packages. But, my impression is that a lot of stuff has been moved into flatpak / snap / etc. just because they can. I don't think it's the best, or even preferred, way to maintain software - for the desktop environment.

(Returns to checking on his Docker containers full of server apps on the R-Pi farm...)

load more comments (5 replies)
[–] HugeNerd@lemmy.ca 3 points 6 days ago

and has it’s purposes

Unlike that apostrophe.

load more comments (1 replies)
[–] ShinkanTrain@lemmy.ml 12 points 6 days ago
[–] LovableSidekick@lemmy.world 10 points 6 days ago* (last edited 6 days ago)

Could things like this go in linuxmemes? Memes are fun but it would be nice to keep this a place for actual information. And no, this is not a comment on what it's saying, I'm just tired of so many memes.

[–] grimaferve@fedia.io 4 points 5 days ago

Honestly? I'm a fan of Flatpaks where they make sense. I'm also okay with Appimages. Native is pretty cool. Whatever gets the thing to run really.

I like to use the terminal to update my applications, it's just faster. I have an alias to run an update for native packages and flatpaks. You can use your GUI of choice. Or not, it's up to you. It's that sort of freedom that I love about using Linux.

In some cases, Flatpak actually helps, as in my case, with Prism Launcher. Some of my system libraries cause issues with a handful of mods, but the libraries distributed with the Flatpak get that working. Hopefully that's not foreshadowing more future library-related issues.

[–] mahi@sh.itjust.works 4 points 5 days ago

I'm a big fan of the idea of sandboxed apps. Flatpak is not great as it compromises sandboxing for compatibility (both with distros and apps) and also it's quite stagnant now. But there are no other options anyway, so I use it.

[–] greywolf0x1@lemmy.ml 5 points 6 days ago (1 children)

Size and gnome/GTK dependencies are main reasons why I don't use Flatpaks (I have nothing against gnome though, it just pulls in too much and KDE is worse in this regards, which is why I use Sway and River)

[–] seralth@lemmy.world 3 points 5 days ago

Naw fuck gnome and fuck GTK. Over invasive and controlling crapware.

[–] SpiceDealer@lemmy.dbzer0.com 7 points 6 days ago* (last edited 6 days ago)

It's a neat concept. The distro-agnostic aspect is definitely a plus for some people but I still prefer distro-specific installation methods. The only time I would seek out the Flatpak version of a particular software is when it's the only version available.

[–] ztwhixsemhwldvka@lemmy.world 8 points 6 days ago (1 children)

I use SystemD binary Gentoo with Flatpaks. Sue me.

[–] geneva_convenience@lemmy.ml 11 points 6 days ago

Watch out we've got a flatass over here

[–] commander@lemmy.world 6 points 6 days ago

I'm happy to use Flatpaks but the annoyances I've had are like when one application says to use you'll need to point to the binary of another application that it depends on but very understandably doesn't package together, figuring that out to me can be annoying so I'll switch to a regular installation and it all just works together no fuss, no flatseal, no thinking about it really. Also some applications where it's really nice to launch from the terminal especially with arguments or just like the current working directory and with Flatpaks instead of just right off the bat it's application name and hit enter, Flatpak hope you remember the whole package name

org.wilson.spalding.runner.knife.ApplicationName ...

Ya alias but got to remember to do that. So far anything I'd ever want to run from terminal, no Flatpak

[–] arc99@lemmy.world 5 points 6 days ago* (last edited 6 days ago) (1 children)

While I wouldn't want flakpak going deep into the OS I think the advantage of using them on the desktop is obvious. Developers can release to multiple dists from a single build and end users get updates and versions immediately rather than waiting for the dist to update its packages. Plus the ability to lock the software down with sandboxes.

The tradeoff is disk consumption but it's not really that big of a deal. Flatpaks are layered so apps can share dependencies. e.g. if the app is GNOME it can share the GNOME runtime with other apps and doesn't need to ship with its own.

FTFY: Flatpaks are layered so apps can share dependencies. e.g. if the app is GNOME 4.2.11.3 it can share the GNOME 4.2.11.3 runtime with other apps and doesn't need to ship with its own, but every app requires a different GNOME version anyway

[–] ipkpjersi@lemmy.ml 8 points 6 days ago* (last edited 6 days ago) (1 children)

I'm not a huge fan of Flatpaks, they're a lot harder to distribute offline versus something like AppImage. Seriously, you have to like create an offline repository, then create a bundle, and it's like 6 or 7 steps, it's honestly kind of ridiculous lol but other than that they seem fine, and they're easy enough to update (but so are apt packages)

I know some people may say "oh why do you need that", but Linux has taught me that my computer is my own, and I should be able to use it the way I want to. I shouldn't have to fight with my package manager to get it to do what I want. So I guess you could say, no I'm not really a fan of Flatpaks.

Personally, I didn't mind Snaps, but I'm getting kind of really fed up with especially for-profit companies etc so I don't like Snap that much now either.

Apt packages are nice, but the more of them you have installed, especially if you're using Ubuntu-based distros and have lots of PPAs, the more annoying upgrading your distro version can be because of all the dependencies and cross-dependencies.

AppImage tends to just work for me, as long as it's not compiled with a newer libc-bin version than the distro I'm currently using has, and I really enjoy that it's just one file I can copy and run pretty much anywhere.

[–] Crozekiel@lemmy.zip 5 points 6 days ago (3 children)

I seem to have constant issues with AppImages. Every single one I have currently won't open. I get an error message relating to either qT or GTK. Tried searching for the error and get a bunch of old forum threads talking about either not being compatible with Wayland at all, or comments stating that the one specific AppImage in question must have been "packaged badly". Thankfully, nothing 'mission critical' for me is an AppImage currently, but it is quite upsetting that I have the most problems with the supposed "just works" app packaging/distribution option.

load more comments (3 replies)
[–] MystValkyrie@lemmy.blahaj.zone 6 points 6 days ago* (last edited 6 days ago) (2 children)

There was a few years where I pretty much only used Flatpaks because I was scared of the terminal. But now that I've learned how to use the terminal, it's so much more convenient because I can quickly update all my applications all in one place without having to open a separate app. Plus, some Flatpaks can fall really behind on software updates.

There might be a Linux userbase someday where no one other than developers actually knows how to use the terminal, because users can run everything they want without a command line, but maybe that's actually a good thing because it'll drive up how many people use a Linux distro.

With Windows and Mac, there's a shareholder incentive to enshittify. With Linux, if a distro goes bad and gets commercialized, there's always another distro people can move to, not to mention there's no financial incentive. The more people get on Linux, the less power these tech companies have. Personally, that and privacy are what drew me to Linux much more so than being able to tinker or fine-tune my experience.

[–] otacon239@lemmy.world 5 points 6 days ago

There might be a Linux userbase someday where no one other than developers actually knows how to use the terminal, because users can run everything they want without a command line

Ideally, all the essential terminal commands could be replicated in a user-friendly GUI-applicable manner. Don’t ever have to remove the terminal for those that enjoy it, but if we could have a magic world where even the failure states could be navigated with little to no prior knowledge required and it gets everyone away from Windows and Mac for good, I’m all for it.

load more comments (1 replies)
[–] mayako@lemmy.blahaj.zone 6 points 6 days ago (2 children)

Personally I am okay with them actually. I use several on my system and having each app allowed to have different permissions is super useful.

But also I like things that are directly installed cause they seem just a tad faster performance wise.

load more comments (2 replies)
[–] AndrewZabar@lemmy.world 5 points 6 days ago (5 children)

I don’t really care about all these different things, as long as none of them become a crazy confusing mess, like Windows DLLs.

load more comments (5 replies)
load more comments
view more: next ›