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
  • 14 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.


  • I never recommend Manjaro, even for experienced users. Multiple times, they’ve let their ssl certificats expire, and renewing those has been easy to automate for a number of years at this point. There have been a number of cases where they ship work-in-progress versions of software as part of their default install, and there was an open letter posted calling this out: https://dont-ship.it

    So in my opinion, Manjaro leaves much to be desired from a project governance standpoint.

    Now, using an Arch-based distro that does the install process for you doesn’t absolve you from learning what it takes to maintain an Arch install; at some point, something will crop-up that requires manual intervention to get back up & running again after an update.

    If that is what you’re looking for, I suggest EndeavourOS.


  • If you want a rolling release, I suggest going with openSUSE Tumbleweed. The installer allows you to pick & choose what you do/don’t want/need, and has a great rollback system in case an update causes problems.

    Otherwise, I would suggest Fedora. Stays very current, and the in-place upgrade process is very seamless at this point.



  • Yeah, the average user: 1) doesn’t care what’s running under the hood, and 2) doesn’t want to control what’s running under the hood.

    I’m definitely not an “average user.” I like specifying that I don’t want wifi, bluetooth, or dvd functionality on my desktop when I have no need/desire to use them. So use flags are one of the main reasons I use Gentoo. Occasionally, it causes some mild irritation, but it’s a net-positive for me.


  • 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.



  • My thinking is, if the normies weren’t motivated enough to move to Mastodon after Musk’s shenanigans, this isn’t going to move the needle very much, either.

    To them, they see it as “hey, they’re making something that’s kind of like Twitter, but I don’t have to create a new login, GREAT,” and not look into it any further. I can see a very marginal percentage that could be curious, but not enough to be that noticeable.

    If more normies actually cared at all about protecting their data, it’d be a different story.


  • In my experience, snaps are better for servers, and flatpaks are better for desktops.

    I haven’t used snaps for a couple years, so they may have fixed this, but I’ve found flatpaks have less issues interacting with peripherals that aren’t mice/keyboards without fenagling with app permissions. A number of snap apps just wouldn’t work without disabling containment entirely (aka “classic”).

    Flatpak permissions can be manipulated from system settings in Plasma, and there’s also Flatseal. I am not aware of an equivalent for snaps; doesn’t mean it doesn’t exist, I haven’t kept up with what’s available for snap for some time.


  • I understand why people are upset, because Red Hat has a communication problem. The way this change was presented was very much “we’re making this change immediately without any warning & nominal explanation.”

    If they presented it as “in 60~90 days, we’re going to make these changes to address such-n-such problems, so we can continue to be sustainable & support the Linux ecosystem,” I’m not sure that the outrage would’ve been as loud or widespread.

    I don’t think a lot of the people yelling at Red Hat realize that Linux wouldn’t be where it is today without Red Had.



  • This doesn’t surprise me. Most people don’t have the time or desire to keep up with tech news, and they just want to feed their addiction. It’ll be interesting to see what happens 1~2 weeks after the new API rules are active, and people realize the app they use no longer works.

    I never created a Reddit account, and only visited under duress, so I’m not really affected by this. So I’m just cooking up popcorn & watching the show.