Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
Stolen from linuxmemes at deltachat
I think this is funny, but it's hard for me to hate too much on flatpaks. Disk space is practically free now, and having spent a good chunk of my career fighting DLL hell, I have a lot of sympathy for the problem it's trying to solve.
Yeah I mean it's taking 500G of my terrabyte ssd. What else was I going to use that for? Installing games off steam? Two node modules folders?
Its good and bad. Bad because the base system cant use it and its not the main packaging choice.
Lots of good apps like OBS use outdated runtimes, which simply should not be used anymore. I am not sure if this is a security issue but probably it is, and it creates this unnecessary Runtime bloat.
Honestly this. It's so nice to not have to hunt for a specific library that depends on 20 other libraries. I'd rather pay in disk space than deal with that.
You also pay in security holes.
I hate this philosophy so much! I hate developers for it! It's like they gave up on even trying to do anything about retrocompatibility and managing libraries and dependancies.
Anyway it will collapse soon. I just wish it was sooner.
Honestly I get both sides of it. Your view makes sense as an end-user and from a philosophical perspective. But some people have legacy software that needs conflicting dependency versions, for instance. It’s just a trade-off.
Yeah, package maintainers should have their dependencies figured out. "Managing dependencies is too hard" is a distro packager's problem to figure out, and isn't a user problem. When they solve it and give you a package, you don't need to figure it out anymore.
Plus, frequent breaking changes in library APIs is a big no-no, so this is avoided whenever possible by responsible authors. Additionally, authors relying on libs with shitty practices is also a no-no. But again, you don't need to worry about dependences because your packager figured this out, included the correct files with working links, and gave them to you as a solved problem.
Some people have limited bandwidth for downloads, and a simple program can run to more space than a basic distro.
I can't use flatpak because each update for a few apps is hundreds of megs and my internet is only 2 Mbps.
That too :-/
it's trying to solve.
It does not solve it. It just slaps more DLLs on top. Package managers do.
Cry-laughing in /nix/store
Me opening /nix/store before bed so I can see it in the morning
I heard they tried to fit node_packages, but the scale caused the sun to become too small to see.
node_modules is so heavy it is the supermassive black hole at the center of the galaxy.
Pro tip: Use /var/lib/flatpak instead of /dev/null for a neater result, you avoid having to clean up spilled bits.
Flatpak: "I would switch from Windows to Linux, but Linux is too bloated"
Still better than snap
Having compared snaps in ubuntu 23.10 to flatpaks on opensuse tumbleweed, I can safely say that snaps tend to be faster for me with less weirdness happening during usage. Some programs were the same (obsidian for example) other comparisons were done from the same category (Firefox snap vs chromium flatpak). I genuinely prefer snap and don't see the issues people often quote. Also, that the backend isn't open isn't a big deal to me, as snaps themselves generally still are.
~$ du -sh /var/lib/flatpak/
6.3G /var/lib/flatpak/
oh my god
Install Gentoo
"Eight Megabytes And Constantly Swapping"
*Terabytes