While they use more disk space than most native packages, this point is often exaggerated. Flatpak uses deduplication and shared runtimes if multiple apps use the same runtime.
but that can and does cause reliability and probability issues.
Flatpak and snaps have been the most broken on this. Just recently I was talking about issues that I had with yuzu on that. And more recently steam as I wanted to test something…
Also I remember you, you were the guy that didn’t reply when you gave a number that I found very odd (Basically impossible lol):
I don’t reply to most comments. You should see my inbox, I have hundreds of undealt with notifications. I only even spotted this reply because I was correcting an autocorrect mistake on my previous one.
My numbers were correct and I explained why.
And your experience is pretty far from mine, I had to give up on appimages because they are problematic by design.
And like I said, Flatpak hasn’t been bad on storage for me. It uses deduplication and unlike you I didn’t go out of my way to cherrypick a small handful of applications that just so happened to use three different runtimes in order to bash it.
Use appimages if that’s what you want, but they’re not really an answer to Flatpaks, due to the huge systematic problems they have.
Do you mind telling me the application list so I can check that myself?
because they are problematic by design.
I didn’t go out of my way to cherrypick a small handful of applications that just so happened to use three different runtimes
Kinda odd, I didn’t even know it was using 3 different runtimes until very recently, I just installed the biggest applications that I had as appimages to make the comparison, and yuzu because I use that one very often lol.
EDIT: Don’t you think that on itself isn’t problematic by design?
in order to bash it.
How should I have phrased my comment so that I wasn’t bashing flatpak?
mmmmm
4.79 GiBwith deduplication.Worth mentioning that my entire distro with those applications included, and about 30 appimages is
4.2 GIBtotal, and that includes the home btw.Appimages don’t use any deduplication at all and usually package everything in the app.
Sometimes they don’t do that though and expect your system to have certain packages, but that can and does cause reliability and portability issues.
E: portability not probability lol
Flatpak and snaps have been the most broken on this. Just recently I was talking about issues that I had with yuzu on that. And more recently steam as I wanted to test something…
Also I remember you, you were the guy that didn’t reply when you gave a number that I found very odd (Basically impossible lol):
https://lemmy.ml/post/16669819/11551689
Were you guy that downvoted the comment btw?
Yes, doesn’t mean anything if flatpak uses way more storage…
I don’t reply to most comments. You should see my inbox, I have hundreds of undealt with notifications. I only even spotted this reply because I was correcting an autocorrect mistake on my previous one.
My numbers were correct and I explained why.
And your experience is pretty far from mine, I had to give up on appimages because they are problematic by design.
And like I said, Flatpak hasn’t been bad on storage for me. It uses deduplication and unlike you I didn’t go out of my way to cherrypick a small handful of applications that just so happened to use three different runtimes in order to bash it.
Use appimages if that’s what you want, but they’re not really an answer to Flatpaks, due to the huge systematic problems they have.
Do you mind telling me the application list so I can check that myself?
Kinda odd, I didn’t even know it was using 3 different runtimes until very recently, I just installed the biggest applications that I had as appimages to make the comparison, and yuzu because I use that one very often lol.
EDIT: Don’t you think that on itself isn’t problematic by design?
How should I have phrased my comment so that I wasn’t bashing flatpak?
Such as?