cross-posted from: https://lemmy.world/post/2287056
I feel like this is a question that might have been asked around and maybe there are guides around, but that's a discussion that I'd like to have with the lot of you.
The context
Using Linux on both my work laptop and the Steam Deck has made me quite interested in a full switch to Linux - my other computer is a gaming desktop, which I use a lot for many things, but mostly for gaming. Getting used to Linux has made me quite more intolerant to all the BS Microsoft is pushing than I used to be, the latest one being forcing the users to switch from the older email client to the new Outlook, which has a big, nice ad banner that looks like an unread email. So I've began wondering: after all, why not? Why shouldn't I embrace the penguin? Well, the answer is that I should not if there are too many hinders and drawbacks in using Linux, which would make me need a dual boot instead of a single OS install.
We all know gaming has long been one of the main limiting factors in switching, but the Deck has changed the whole landscape on that front. We've basically switched from "Windows is the only OS suitable for gaming" to "Linux is also viable", and the Deck has been made that available to the general audience. Therefore, nowadays, how viable is Linux for a gaming computer? What are the limitations users will encounter? Would I be able to play all the games from my Steam, Epic and GOG library with a bit of tinkering, including the new releases?
The drawbacks of using Linux (or those that I can think of)
- Other gaming launchers support on Linux suck: GOG and Epic will work through Heroic Games but Activision/Blizzard, Ubisoft, EA and Rockstar games will all be a pain, or even not work at all. Is is true? Is there any way around that?
- No Microsoft GamePass. Or none that actually matters, as the only solution is to pay for the higher tier and stream the games - so no game actually runs on the desktop. No, thanks.
- Some DRM will prevent games from working, and this is especially true for games with heavy online content.
- NVIDIA support for Linux is far from being on-par with that on Windows, especially the open-source drivers. Is this still true?
- Many devices, especially those for gaming, might not have good (or even working) compatibility drivers for Linux. I know my UWQHD monitor works flawlessly on Windows, but requires quite a bit of tinkering on Ubuntu
- Newer games might not be optimized for Linux in the first place
- Tinkering is inevitable (as with any Linux computer, really)
What can we add?
The advantages (I can think of)
- It's free
- It's ad free
- Customization on Linux is awesome, and I might end up spending more time ricing, breaking it all and reinstalling than gaming (see also, previous section's 7.)
- I will no longer be sending data to Microsoft
What else am I not thinking about?
What distro?
And finally, let's say I make the switch. What Linux distro should I use? I've read a bit about Drauger, Ubuntu GamePack, or even Pop! OS with some manual setup. What do you guys think, and advise?
I've been gaming on Linux exclusively for 5 years now. I like it, but it's not perfect.
Experience
Pros
Cons
Picking a Distro
There are a lot of pitfalls when choosing a distribution. I can't personally tell you which one to pick, so instead I'll give targetted advice.
Things to avoid
Avoid Ubuntu. Avoid Fedora/RedHat/CentOS. Avoid any distro with less than 5 years of active development history. Avoid niche single-purpose distros, including gaming ones. Probably also avoid NixOS until you're more comfortable with Linux in general.
tl;dr: Pick something that's very popular, but not Ubuntu. Ideally, the project should have multiple full-time donation-supported maintainers and a detailed wiki.
Rolling Release vs. Point Release
A "point release" distribution is one which guarantees a certain level of stability out-of-box. It achieves this by partially freezing the available packages at well-tested & known working versions (explanation simplified for brevity). This way, when you install the distro, there are very few or even no "gotcha" moments where one niche part of the system randomly breaks during daily usage.
The downside of this strategy is that, over time, the packages on your system get more and more out of sync with the rest of the world. Eventually, you have to sit down and do a big, fat upgrade to the latest version. This has the effect of potentially breaking lots of things all at once, which makes upgrading these systems comparatively onerous.
A "rolling release" distribution has no numbered versions. You just upgrade your packages and presto: you're rolling the latest code. Yes, there are more day-to-day difficulties, though you generally experience fewer cascading catastrophic failures, since usually only one thing will go wrong at a time. The risk of day-to-day issues is then addressed by splitting the distribution into time-gated "channels" where new package releases are intentionally delayed for days/weeks based on which one you've opted into. This gives you as a user flexible control over how current vs. stable you want your system to be.
tl;dr: For most newcomers, I recommend using a rolling release set to the safest available release channel. It offers most of the day-to-day stability of a versioned release with none of the upgrade headaches. These days, I feel that versioned releases are mostly only preferable in corporate/institutional usecases (this is a controversial, personal opinion and not a statement of fact, but I welcome flamewars down below...)
Wayland vs. X11
Wayland replaces X11 (which is old and bad)... but it also breaks compatibility with stuff. If you use Wayland, you will have more issues, so I generally recommend newcomers choose X11 if the installer gives them an option.
With that being said, sometimes you have to choose Wayland because you need its modern features, such as display scaling. If you have a >1440p monitor or use monitors with mixed refresh rates, this probably includes you. It's not the end of the world, but you'll have to deal with learning to troubleshoot Wayland's various quirks as you go.
tl;dr: Use X11 if you can unless you have big/weird monitors. Wayland's still very workable though, despite what reputation would otherwise suggest.
Gnome vs. KDE vs. Other
Gnome/KDE are what we call "Desktop Environments". I won't dwell on the terminology too long because it's a mess, but basically these are the two major "all-in-one" kits that distros tend to bundle for their sytem GUIs. Gnome is the usershare king, so it's generally the most well-supported by other desktop software and therefore my default recommendation. KDE is mostly interchangeable with Gnome, though it's a pretty distant second usage-wise.
There are many alternatives to Gnome/KDE, such as the lightweight LXDE, but I generally don't recommend these to newcomers unless there is a strong reason. This is because desktop apps can have all sorts of weird bugs if they can't find a specific Gnome or KDE version of a certain components (e.g.: polkit).
You can also build your own desktop environment from scratch, which is actually what I do. This allows for maximum ricing, but obviously isn't a great starter situation. Even if you eventually do want to roll your own environment, I recommend newcomers start with either Gnome or KDE as a base and then slowly replace individual pieces as they go, ship-of-theseus style.
tl;dr: Just use Gnome and eventually rip out the parts you don't like. KDE is a good alternative if you really like it, though.