2025 has probably been the best year for Linux that I can remember, at least from the perspective of general PC users. It's had tons of publicity as a viable alternative to Windows, even, and perhaps especially for gaming. I switched to it myself earlier this year, but I'm back on Windows and I don't think I'll be switching back to Linux properly any time soon.
The Linux hype this time was precipitated by Valve's Linux-based operating system, SteamOS, opening up for use on other handhelds than just the Steam Deck. That had been long on the cards, but it finally started seeming close at hand early on this year.
SteamOS has shown what Linux can be capable of for gaming in large part because of Proton, the compatibility layer Valve employs to translate Windows commands into ones that Linux can understand. It's a fork of WINE tailored towards gaming, created and maintained by Valve specifically for that purpose.
Over the years, Proton has gotten so good that compatible games tend to run flawlessly. Valve has an incentive to ensure this is the case, as a great gaming experience on SteamOS via Proton makes for more Steam Deck and Steam Store sales.
The development and improvement of Proton has been a massive part of what's made Linux distros genuinely viable for gaming. And yes, I said "distros", plural, because any distro can use Proton, as it's built into Steam for Linux. It's not just a SteamOS thing.
My own recent foray into Linux was very short-lived, however. I've dipped into Linux many times over the course of my life, but I've never stuck with it, and this time I was punted back over to Windows with undue force. You can read the full story explaining why here, but the long-story-short is it just completely broke—trackpad, Wi-Fi card, the lot—while I was working away at Gamescom, and I didn't have the time or patience to troubleshoot and fix it.
A frantic Windows install was my solution, and the experience has traumatised me enough that I'm reluctant to give Linux another go, at least not on a machine that I depend on for work. I'd experienced troubles that made me consider abandoning Linux prior to this—Nobara Linux didn't seem to gel with my laptop's hybrid graphics and external monitor—but my complete disaster at Gamescom solidified things.
Still, that was just my own experience, and the hype was still there for Linux as the year went on. Whether that was from influencers and publications capitalising on the hype by generating even more hype, or whether it was real enthusiasm, it doesn't matter: it was there.
That was a lot of reading to learn that the two things were:
He had some kind of problem with the laptop Wi-Fi driver on his new install of Ubuntu, and — pressed for time, away from home — decided that the best way to fix it was to reinstall Windows.
He's unwilling to give up games whose devs have chosen to make them impossible to play on Linux. It's not clear which one he's hooked on, but Apex Legends, to Fortnite and Valorant are mentioned.
oh my fucking god he wrote basically this same exact article when the first thing happened.
i shouldn’t know more about tech than tech journalists, this is obscene.
Journalism is dead, in general
The first one. Away from home he decides to try one Linux distribution, something he apparently has no experience in and with not much extra time to spare? Wow, what a great reason.
The second one, yeah. If you are used to playing these games I get it. I never even got into those, so have no need to start them now.
I mean, yes, he should've picked a less busy period to test Linux out. But trackpad and wifi issues could come up at any time, which would be troublesome. I've gone weeks wihout issues, only to turn my laptop on one day and boom, touchpad doesn't work. And some days I don't have my mouse with me to use. And the other issue is Linux is so varied and different that a solution for one person might not work for you. That and lack of proper documentation. I have tried doing crazy shit to fix issues, only to then learn all I had to do was toggle a switch in the settings, but my distro didn't make it obvious that's what i should do.
(This LITERALLY is what happened with my touchpad, for some reason it disabled itself in settings after an update a while ago.)
People don't want to spend weekends fixing their tech, and that's understandable.
I mean, they could have pretty quickly and easily tried a different distro
For the past month or so, I've been getting "RDSEED32 is broken" and it seems to be an issue with AMD's drivers? Either way, there doesn't appear to be a solution for me outside of getting a new CPU, but it also still boots and works so I'm not too bothered by it either.
But when updates roll around? Yeah, usually a good idea to make a backup before updating. Same is true with Windows, of course, but I already expect Windows to need a reinstall every year or so.
https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7055.html
it sounds like the kernel is just working around a known CPU microcode bug. it would probably be using the 64-bit RDSEED operation anyway, so disabling the 32-bit option probably doesn't actually change anything.
also, the kernel's random number generator is very robust (especially since Jason Donenfeld, the author of Wireguard, took over its maintenance) and will work perfectly fine even in the complete absence of RDSEED CPU instructions.
Yeah that particular issue doesn't bother me much anyway, just delays startup by a second or two.
If that's the games he plays then he deserves Windows.
Funny enough, I've only had that problem with Windows. Both for my Steel Legend motherboard, and a Framework laptop I setup as a gift with Windows.
Thanks. I saw the bit about the WiFi card and trackpad, but missed the games he plays.
Before I got my Steam deck I did all of my gaming on a MacBook, ps5, or switch. If it was not available on one of those platforms I never looked at it.
Even now when buying a game I lean towards those playable on Mac.