|
Top-level
 @Ray_Of_Sunlight @r1w1s1 @srtcd424 @keepassxc @j_r @lieven I like flatpak, but prefer to use native packages when I can. Their choice sounds like a dubious one, but as long as there's still a native package with the feature I need, I'll be using that one. 4 comments
 @srtcd424 I do like the "bundle with all dependencies", although it makes the package a lil' heavier, it helos not having to download the dependencies on separated servers and who knows when one of them will shut down. Plus, it's cross-distro and it's not like Snaps. @srtcd424 @Ray_Of_Sunlight @r1w1s1 @keepassxc @j_r @lieven Personal choice, of course. I generally don't see the need to have the absolutely latest version of everything. I don't mind being a couple versions behind in Audacity, or using Firefox & Thunderbird ESR. There *are* times where having the latest is more important, where the older versions lack some critical functionality, and for that, I use flatpak. It's all good. ;) |
Gregory's Server
@RL_Dane @Ray_Of_Sunlight @r1w1s1 @keepassxc @j_r @lieven I've settled in on flatpaks for "key" or major apps - keepassxc isn't large, but I do consider it important. Allows to me keep on a stable distro and still track up-to-date versions of things.
I'm not really a huge fan of the "bundle all dependencies" model, but I've grudgingly accepted that's the world we're in now, and disk is still cheap relative to app sizes even given modern toolkit bloat!