• 1 Post
  • 56 Comments
Joined 4 years ago
cake
Cake day: February 19th, 2021

help-circle





  • Benefits any software dev on Linux, as flatpak ships all your dependencies in one “container”. This allows you to deploy once and forget about whether some Ubuntu system dependency is on the same version/compatible with your test environment. Software that works everywhere is the biggest win of flatpaks. One could also make the same argument for snaps except the package repository is closed-sourced.

    For me, it allows an easy configurable sandbox with Flatseal. This is the main reason I use flatpaks TBH, software is packaged with too much express permissions on Linux. You also get delta updates. Plus I don’t have to worry about mucking around with system packages if for example some dependency is not available or needs building/installing.





  • Disagree. Arch is not stable at all, couldn’t be even if you wanted it to be.

    Bugs and regressions get introduced upstream all the time, these have a tendency to slip from testing into the main repos.

    Case in point, a recent glib2 update was causing NetworkManager to coredump sporadically.

    And you have to always use downgrade. Example, the newer 6.5 kernels break thermald 2.5.4 for me, so I have to downgrade a step downwards.

    Are these problems because of Arch? Not necessarily but the rolling release model has a role to play in these types of regressions & bugs.

    An LTS type of distro will face other different types of bugs. Outdated software libraries/dependencies that are rendered incompatible etc.

    But these are few and far between compared to rolling release where everything is in a constant state of change.