An eclectic #nerdy #weirdo.

In addition to tech, #Linux, and other things #FLOSS, I’m also into #travel, jam bands (mostly Grateful Dead), music festivals, and anything related to exploring the #cosmos.

All puns are intended.

#actuallyautistic #deadhead #hockey

  • 0 Posts
  • 6 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle


  • “Stable” doesn’t necessarily refer to “reliable,” depending on the context. Stable is often used in reference to how often a distro releases new versions of the applications. Using Audacity as an example, in the current release of the distro, they’ll release security & bug fixes for version 2, but if you want version 3, you’ll have to wait until the next distro release.

    Upgrades to a new version of an application can introduce new ways of using the app (i.e. icons in different places, how user-created files are written to disk, etc.), which is disruptive to enterprise op’s, which is why Debian & RHEL take this approach.

    Hopefully that helps clarify things.



  • I definitely prefer it over Snaps or appimages. Straight-forward to update, and Flatseal provides a nice GUI to control permissions (if needed). Themes may not work properly, but whatever, not a big deal for me.

    The distro’s repo is always my go-to. If it’s not available there, then flatpak, and I’ll use appimage under duress. If that doesn’t work, I’ll figure out a different solution.


  • Can’t say that I’ve really used any of the features mentioned in this list, so doesn’t really affect my experience negatively. Also, updating some icon sets to fit with the overall theme would provide a more unified experience. So two thumbs-up from me for removing code that, by & large, wasn’t getting used, should help maintaining it in the long run.