• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • To answer some of your questions:

    1. Fedora has two major releases per year. I’ve only been using it long enough to do one upgrade, but it was basically seamless and the same as any normal incremental update, except it took longer to apply.
    2. I can’t speak for other DEs, but the Plasma spin provides a system setting to apply updates automatically. I haven’t used it myself, but it’s literally just a radio button so I imagine it’s pretty easy to get working.
    3. SELinux for the most part is unobtrusive, but it can definitely be a pain when trying to do more advanced things on the system. For instance, it needs to be specially configured to allow systemd-hibernate to work, and I still haven’t gotten hibernate-after-sleep to work at all (though that might not be SELinux’s fault, I haven’t found time to follow up on it. You can also disable it, though, if it gets too much in the way.

    I can’t speak to Arc support or RAID specifically, although if the data on the RAID array is vital then you NEED to have at least one backup before you even think about installing a new OS.













  • It most certainly is not. Besides the missing features mentioned by the other commenter, SteamVR 2.1 literally shipped last week with a bug that caused it to completely stop functioning on Linux. I think the hotfix version still isn’t in the release channel. There’s another bug still present in 2.1.7 that prevents VR games from starting. SteamVR Home doesn’t work at all anymore.

    2.0 had an issue where vrdashboard was using the wrong pixel format which caused the red and blue channels to be swapped (pretty sure that made it into the release channel), and there was a regression introduced in the last year (and is still yet to be fixed) that causes vrdashboard to be rendered to the controller instead of the battery indicator. Granted, these are more minor issues, but it shows the level of QA that goes into the Linux version (next to none).




  • Public companies are by definition amoral. They’re beholden to their shareholders and virtually every decision they make is informed by this obligation. Morality generally only factors into their decision-making insofar as it affects PR and thus the bottom line.

    I don’t mean to say that Google or any other company is immoral. I use amoral to simply mean that they operate independent of morality. No public company, no matter how much you may like them, is your friend at the end of the day.


  • Chromium is open-source. Chrome is not and also happens to constitute a majority of the browser market, and Google has tried multiple times to cash in on this market share to benefit their primary business of advertising to the detriment of users (FLoC, Manifest v3, Web Environment Integrity).

    Likewise, AOSP is open-source, but Google has been progressively dismantling it and making various components closed-source (most recently the dialer app).

    All this to say, Google is absolutely not friendly to FOSS. As a corporation, they’re beholden to their shareholders above all else and they should be treated as an amoral entity, the same as every other publicly-traded company.


  • As another user mentioned, package managers are specific to distributions rather than DEs. The main difference between them is that they’re developed by the respective distribution teams, but there are some practical differences too. For example, apt supports versioned dependencies while pacman doesn’t because of the different distribution models between Debian and Arch (monolithic vs. rolling release). This affects their dependency resolution strategy with each being better suited for it’s respective distribution.

    To address your point about package managers being the main difference between distros, this isn’t quite true. As mentioned, different distros have different distribution models, priorities, and overall biases/opinions that affect the user experience in a variety of ways and make them better suited to different use cases. I would never dream of putting Arch on one of my servers in the same way that you’d probably never catch me installing Debian on my gaming machine.