0
submitted 1 year ago by Glome@kbin.social to c/linux@kbin.social

TLDR at bottom.

On most linux forums, it seems that everyone is trash talking flatpaks, snaps, docker, and other containerized packages with the statement that they are "pre-compiled". Is there a real-world affect that this has with performance and/or security, and does this have to do with canonical and/or redhat leaving a bad taste in people's mouths due to previous scandals?

Also, it is easier for the developer to maintain only one version of the package for every user. All of the dependencies come with the package meaning that there aren't distro-specific problems and everything "just works" out of the box.

I understand that this also makes the flatpaks larger, but there is deduplication that shrinks them as you install more by re-using libraries. Do the drawbacks of a slightly larger initial disk usage really outweigh all of its advantages?

I have heard that flatpaks are slower than distro-specific compiled binaries but haven't seen a case where this affects performance in the real world.

TLDR: In most forums linux users tend to take the side of distro-specific packages without an explanation as to why.

you are viewing a single comment's thread
view the rest of the comments
[-] cinaed666@kbin.social 1 points 1 year ago* (last edited 1 year ago)

https://github.com/obsproject/obs-studio/pull/2868

This is a good example of this kind of evangelism for the hot new packaging standard gone wrong.
A pull request was made for a half-baked appImage version of OBS by appImage creators.
They refused to support it, and the OBS developers refused to merge it because they have no appImage knowledge.
Drama ensued.

I do like how nixOS is tackling this issue, but I don't really care enough to switch away from Arch.

this post was submitted on 16 Jul 2023
0 points (NaN% liked)

Linux

59 readers
2 users here now

founded 1 year ago