Linux

48330 readers

578 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

108

Flatpak is only for graphical apps - Flatpak's biggest flaw? (iusearchlinux.fyi)

submitted 10 months ago by Libretto@iusearchlinux.fyi to c/linux@lemmy.ml

41 comments fedilink hide all child comments

I love Flatpaks, the programs are nicely separated so they don't interfere with each other. They also don't have flaws like Snap's low performance or Nix's complexity.

But being limited to only graphical apps seems like a real drawback. If one wants to use Flatpaks as their primary package manager there have to be some awkward workarounds for cli programs.

E.g., the prime Flatpak experiene is supposed to be on immutable distros like Silverblue. But to install regular cli programs you are expected to spin up a distrobox (or toolbox) and install those programs there.

Having one arch distrobox where I get my cli programs from will not work, as the package entropy over time will get me the very dependency issues that Flatpak wants to solve.

So what is the solution here? Have multiple distroboxes and install packages in those in alternation and hope the boxes don't break? Use Nix alongside Flatpak? Use Snaps?

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

[+] ExtremeDullard@lemmy.sdf.org -23 points 10 months ago* (last edited 10 months ago) (4 children)

Flatpaks are disk and memory hogs, and they start slowly. That's because they're like little selt-contained full-fledged operating systems.

Flatpaks, like snaps, applimages, dockers, Electron apps, React apps or Flutter apps are the lazy 21st century developer's way of achieving cross-compatibility without any effort.

[–] Montagge@kbin.social 16 points 10 months ago

I always like comments like this that don't offer the "real" solution

[–] vfosnar@beehaw.org 9 points 10 months ago

That's not true and misleading. Docker and flatpak base images mostly contain shared libraries and even these get automatically deduplicated. Your flatpak calculator doesn't ship systemd or any other init system nor does it ship system drivers lol

And yeah if you are working in a restrained env and care about those few mbs taken by shared libraries then containarization is not for you.

Containerization is not perfect and it will never be, but that was never the goal. Making apps and services independent of the base system and easily restrictable like mounting volumes, restricting network, etc.. was.