Free and open-source.

Receives regular software and kernel updates.

Avoids X11.

The notable exception is Qubes, but the isolation issues which X11 typically has are avoided by virtualization. This isolation only applies to apps running in different qubes (virtual machines), apps running in the same qube are not protected from each other.

Supports full-disk encryption during installation.

Doesn’t freeze regular releases for more than 1 year.

We recommend against “Long Term Support” or “stable” distro releases for desktop usage.

Supports a wide variety of hardware.

Preference towards larger projects.

Edit: I’m new to linux

  • throwawayish@lemmy.ml
    3·
    1 year ago

    I’ve already written another comment here. But I just noticed that you have edited OP’s text to include that you were new to Linux. Which changes the rules of the game so much so that a simple edit of my other post wouldn’t do it justice for the sake of visibility. Btw, perhaps you should have told us that earlier 😅.

    So previously I had named Arch, Fedora and openSUSE Tumbleweed. These distros are still definitely worth the trouble. However, instead of Arch directly, you might wanna opt to an Arch-based distro. They often come with an installation that’s done through a GUI, which you might perhaps conceive as being more intuitive. Though, there are some that argue anything Arch-related is not suited for new users. Personally, I don’t buy into that. But there’s definitely some truth to it in the sense that other distros might be better suited for some new users. We don’t know what ‘type of new user’ you are, therefore we won’t be able to answer that for you. However, my gut feeling tells me that you’ve got some potential to start out with (an) Arch(-based distro) right out of the gate. Though, I’m not very confident (yet)😅.

    With that out of the way, I think the following is important to note as well:

    • If you want to avoid X11, then you have to use Wayland. Which, in turn, implies that you’ve got to use either GNOME or KDE as your desktop environment. Unless, of course, you want to try out a tiling window manager (like Sway or Hyprland etc) right out of the gate as well. Which, again, doesn’t make it easier for you to start using Linux 😅. It’s definitely worth it eventually, but perhaps it’s better to not make it too hard on ourselves from the get-go. Coming back to GNOME and KDE, fortunately they’re very well-supported on the previously mentioned three distros. So you should be fine regardless. As to which of the two suits you best…? Well, that’s very personal. An oversimplified overview would be that GNOME is polished and ‘limited in regards to customization out-of-the-box’ while KDE allows you to customize to your heart’s content at the cost of polish. GNOME does have support for extensions that allows it to be easily customized beyond what KDE allows one. However, this comes -once again- at the cost of polish 😅. It’s best to make your own mind with this. Use both of them, and come to judge them yourself.

    • So I can’t but notice that you’re sensitive to your digital security (which is good thing 👍), but that you’d like your distro of choice to do the heavy lifting; which is totally fair. In that case, I would argue that Fedora and openSUSE Tumbleweed are better suited than Arch(-based distros), because they’re distros that take security very seriously. Heck, they’re the only popular ‘upstream’/‘independent’ distros that have managed to configure SELinux for use on their distros. On Fedora this is done by default regardless, while on openSUSE Tumbleweed it can be installed at a later point. (IIRC openSUSE Aeon/Kalpa (old MicroOS Desktop) shipped with SELinux by default, but the linked article suggests otherwise 🤔.) In contrast, while you can make it work on Arch, it’s not officially supported. AppArmor is still great though*.

    • If security is indeed important to you, have you perhaps considered using so-called ‘immutable’ distros? Btw, the name ‘immutable’ is not entirely correct as in most cases only some parts (mainly related to base system components) are read-only during runtime; changes to said base system components (through either installing/remove a package or upgrading) happens atomically and often times requires a (soft-)reboot to actually take effect. Some ‘immutable’ distros even manage to be reproducible and yet some actually manage to be declarative as well. The security-benefits for this can’t be overstated. If you’re interested in ‘immutable’ distros, then it’s worth mentioning that both Fedora and openSUSE offer them through Silverblue/Kinoite/Sericea and Aeon/Kalpa(/Greybeard) respectively. The exact implementation of ‘immutability’ across Fedora’s and openSUSE’s offerings are different. However, I won’t go over that for the sake of brevity 😅.

    Please feel free to inquire if you so desire!

      • throwawayish@lemmy.ml
        3·
        1 year ago

        That’s perhaps a bit too open of a question to ask 😅. But I’ll give it a try:

        I’ll assume the following:

        • You asked specifically for the ‘immutable’ distros that are intended to be used on desktop. Which, moving forward will be referred to as ‘immutable’ desktops.
        • You asked me to look at them in a ‘vacuum’, thus not comparing it to other ‘immutable’ desktops. Or at least, it shouldn’t be the primary focus.

        So without further ado:

        • Out of the earlier named ‘versions’, Aeon (GNOME version) is clearly the most polished and the only one I would actually recommend using. Regarding Kalpa (KDE version); just a few months ago its (then) most active maintainer had stated the following:

        ‘I am stating, right now, for those of you that are clamoring for it to be so, or asking when it will be “release ready” that microOS Desktop Plasma, is not, and will not be “release ready” anytime soon.’

        This, indeed, is quite worrisome 😅. Unfortunately, Greybeard (Sway version) is arguably even less production ready… So for starters, if you want to use any of openSUSE’s ‘immutable’ desktops, then you should definitely use openSUSE Aeon.

        • Regarding the inner-workings of openSUSE’s immutable desktops: -though this is merely an oversimplification- one could understand it as openSUSE Tumbleweed’s model with some ‘extras’. With those extras being:
          • The base system components of the currently running system is snapshot and copied
          • Changes (be it installing/removing packages (natively) or upgrading base system components etc) are applied on the newly copied snapshot atomically; which means it either happens or doesn’t. There’s no in-between state, even with power outages and whatnot. Thus guaranteeing that a lot of the complexity with updating that would be found on traditional systems is removed. Btw, atomic updates is almost like a basic requirement with how prevalent it is on any distro that’s considered ‘immutable’.
          • After the changes have been applied successfully, the copy is made read-only.
          • Changes are then supposed to require a (soft-)reboot for them to take effect.

        As this model is relatively ‘simple’ compared to other immutable distros and doesn’t seem a radical departure from traditional systems, one might expect a lot of things to ‘just continue working’. However, I’m not confident if that’s actually the case. Though, I’d love others to chime in and tell us their experiences. This more simple model does come at a ‘cost’ though; as it stands, this model is not declarative, nor is it reproducible. Which are qualities found on some other ‘immutable’ distros.

        • The implementation of its release cycle, however, is a major win for openSUSE’s immutable desktops and probably the best reason for choosing it over the others. For years openSUSE has pioneered what a stable rolling release is supposed to look like with their Tumbleweed. And its immutable desktops continue to benefit of this. So while blendOS, Fedora (on Rawhide) and NixOS (on unstable) technically are other ‘immutable’ distros with rolling release cycles, one simply can’t deny that they’re inferior (in the rolling release aspect) compared to openSUSE’s immutable desktops.
        • On a final note, I’ve often heard that openSUSE’s ‘immutable’ desktops have more ‘sane’ defaults compared to some of the others. Things like offering Firefox as a flatpak instead, shipping Distrobox by default or installing flatpaks not system-wide but per user etc. These might seem like little nitpicks, and arguably others might simply not agree with these choices. However, I agree that generally-speaking most users should prefer these defaults.

        Please let me know in case you were expecting a different type of answer!

        • guilty_tangent@lemmy.fmhy.net
          2·
          1 year ago

          That was perfect! Thanks for sharing. 🙂

          I myself haven’t used any of the immutable desktop offerings yet, but I do have some familiarity with openSUSE which was why I asked.

          It does sound alot like they are taking time tested designs that have been in use in the datacenter & Infrastructure side within virtualization offerings for years & applying them to a desktop OS, which is very interesting.

          • throwawayish@lemmy.ml
            1·
            1 year ago

            That was perfect! Thanks for sharing.

            Thanks for your kind words. Much appreciated! 🙂

            It does sound alot like they are taking time tested designs that have been in use in the datacenter & Infrastructure side within virtualization offerings for years

            To be honest, I’m absolutely clueless on any of that 😂. So, unfortunately I don’t feel confident to talk about that. Would you be so kind to enlighten me?