Linux

48372 readers

1690 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

172

Is there a downside to Flatpak? (lemmy.world)

submitted 9 months ago by 0485919158191@lemmy.world to c/linux@lemmy.ml

166 comments fedilink hide all child comments

Basically title.

I’m wondering if a package manager like flatpak comes with any drawback or negatives. Since it just works on basically any distro. Why isn’t this just the default? It seems very convenient.

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

[–] Pantherina@feddit.de 13 points 9 months ago* (last edited 9 months ago) (1 children)

no OS level components
duplicate libraries as some core apps (editor, filemanager, Desktop) cannot be flatpaks (yet?)
old runtimes etc. dont force developers to keep them updated. Often thats because or 3rd party packagers though
complicated packaging, I heard that the Flatpak builder is better for certain languages.
theming issues I heard (on Fedora Kinoite Wayland it just works, and I can also force themes per app)
bad permissions by default (best we have though)
bad run commands (this could easily be fixed, and I have a script for it)

For OS components / packaging every part, Snaps may work, but for GUI apps they seem subpar and nobody really cares.

Nix may be way better for installing just anything compartimentalized, but there is no permission system (thats why packaging is easier).

But Flatpaks are really great overall, Bubblewrap, KDE Settings / Flatseal, Portals, official app support. Its really really important.

[–] justin@lemmy.kde.social 2 points 9 months ago (3 children)

complicate packaging, XML sucks (are there good editors or something?), I heard that the Flatpak builder is better for certain languages.

What has XML got to do with it? Flatpak manifests are either JSON (not great but OK) or YAML, which is great.

[–] kamiheku@sopuli.xyz 17 points 9 months ago

YAML, which is great

countries:
  - fi
  - se
  - no
  - dk

=> { "countries": ["fi", "se", false, "dk"] }

[–] corsicanguppy@lemmy.ca 1 points 9 months ago

YAML, which is great.

Well, someone had to finally believe that.

[–] Pantherina@feddit.de 1 points 9 months ago (1 children)

Weird? One I saw was XML or maybe JSON

[–] justin@lemmy.kde.social 3 points 9 months ago

Probably JSON. I haven’t been involved in Flatpak for a long time but I’ve never seen XML. JSON is quite close to XML in it’s layout sometimes I find so easily mistaken.