That headline is not a contradiction. It’s the most honest thing I can tell you about Linux in 2026.
Let me explain both halves.
Where This Started — A 386 and No Frame of Reference
My first encounter with Linux was on an Intel 386. I would have been 15 to 18 years old. Second computer I’d ever used.
To be clear about what that means: this was not a gentle introduction. Linux in that era was not for people. It was for the specific type of person who genuinely enjoyed fighting with a machine to make it do anything. There was no Ubuntu. There was no Mint. There was no installer that held your hand through the process. You were looking at Slackware, maybe early Debian, maybe Red Hat if you were lucky enough to know it existed — all launched between 1993 and 1994 — and none of it was in the same conversation as DOS or Windows 95 for actually using a computer.
I went back to Windows. The right call at the time.
The Dialup Days — The Hardcore Crowd Emerges
Through the late 90s and into the early 2000s — dialup era, forums, the early internet — you started seeing circles of Linux users form online. Red Hat was gaining enterprise traction by 1998, Linux market share was actually rising significantly that year. Arch Linux arrived in 2002 as the minimalist, build-it-yourself option for people who considered Red Hat too easy.
Ubuntu didn’t exist until October 2004. Before that, if someone was running Linux as a desktop daily driver they were either a server administrator, a hardcore developer, or someone with a very specific kind of patience.
The community was real but narrow. And critically — nobody who gamed seriously was running Linux. The gaming ecosystem was Windows. That wasn’t a preference. It was the only viable option. DirectX, driver support, titles — all of it was Windows-first or Windows-only.
So Linux stayed as something I watched, experimented with occasionally, and kept at arm’s length while Windows ran the actual work.
2018–2020 — The Shift
This is when the equation changed for me.
Not overnight. Not one moment. A slow accumulation of reasons that tipped the balance.
Home lab expansion — running serious infrastructure at TrojanHQ meant Linux wasn’t optional. Servers, VMs, NAS, networking — the professional world runs on Linux because Linux is better at being a server than Windows has ever been. The enterprise world figured this out in the late 90s. I was building the same infrastructure at home. The answer was the same.
Development work — the more serious the development, the more Linux made sense. Package management that actually works. A terminal that does what you tell it. Python, Node, Docker, Git — all of it runs natively on Linux without the layer of friction Windows adds. The toolchain just works.
Windows accumulating its own problems — updates that restart your machine at the wrong moment. Telemetry you didn’t ask for. Bloat on every fresh install. The slow creep of an OS that increasingly treats you as a product rather than a user. None of it was one fatal blow. All of it was weight that built up.
By 2020 the TrojanHQ production stack had shifted. The Xeon servers run Linux headless. The NAS runs Linux. The Pi monitoring nodes run Linux. The infrastructure that runs this entire operation — website, forum, FiveM server, AI inference, development VMs — runs on Linux.
The Distro Question — My Actual Recommendations
I’ll keep this practical rather than religious.
For the gamer who wants Linux: Garuda Linux — specifically the Dragon edition. Arch-based, gaming-optimised out of the box, performance tuning baked in. This is the honest answer for a gamer switching to Linux. Not Bazzite. Not the gaming-branded distributions being pushed right now.
Here’s the Bazzite burn, and I mean this constructively: Dolphin file manager is a disaster. It has suffered idle network delays and holdups that simply do not exist on any other file manager. I have tested file managers across everything from 286-era machines to now. The problem is a known design flaw the developers refuse to fix. In 2026, having to change your OS’s file management system because the default one has a networking bug the team won’t address — that is a fundamental failure. It cripples the daily use experience and it’s the reason I cannot recommend distributions that ship it as default without a warning attached.
For security out of the box: Pop!_OS — System76 deserve significant credit for what they’ve built here. Best security posture of any consumer Linux distribution without configuration. Has been since before 2020. If someone at System76 is reading this, you should sponsor TrojanHQ, I’ve been recommending you for years without compensation.
For the newcomer who just wants it to work: Linux Mint over Ubuntu for most people. Ubuntu is not wrong — Debian and Fedora are legitimate choices and the community that snubs them as “noob distros” are wrong. Ubuntu runs the back end of a significant portion of the world’s infrastructure. It is not a beginner toy. But for a home user making the switch from Windows, Mint’s interface, hardware compatibility, and out-of-box experience makes the transition easier.
For the serious developer or tinkerer: Arch — if you’re willing to invest the setup time. The knowledge you build installing and maintaining Arch is more valuable than the OS itself. You will understand your system at a level that pre-configured distributions cannot teach you.
Ubuntu, Debian, Fedora — accepted. Widely used in corporate and enterprise environments because they’re stable, well-supported, and well-documented. Anyone telling you these are only for beginners hasn’t worked in enterprise infrastructure.
What the TrojanHQ Fleet Actually Runs
To give this context — this isn’t theoretical. The TrojanHQ production infrastructure:
-
Xeon Alpha, Beta, Prime — headless Linux servers. Website, forum, FiveM server instances, development VMs, AI inference
-
NAS Prime and NAS Secondary — Linux. 32TB and 12TB storage pools
-
Raspberry Pi nodes — Linux. Monitoring and automation
-
Firewall appliance — Linux (OPNSense)
-
Development VMs — Linux
Windows runs on KING — the primary development workstation. And on gaming rigs. Because of one thing.
Why I Still Use Windows — The Honest Answer
Games.
That’s most of it. The gaming ecosystem is still primarily Windows. Steam on Linux (Proton) has improved dramatically and continues to improve. A growing number of titles run well. But “growing number” and “all the games I want to play without friction” are still not the same sentence in 2026.
For a pure Linux gaming setup — Garuda Dragon gets you the closest. Proton compatibility has come further than most people realise. But some titles still don’t cooperate. Anti-cheat implementations, specific DirectX dependencies, titles that simply haven’t been tested — the friction exists and pretending it doesn’t would be dishonest.
There’s also specific software. Some workflows. Tools that are Windows-first with no Linux equivalent worth using.
The workstation that runs development, AI sessions, FiveM scripting, book production — that’s Windows because the primary GPU (RX 7900 XTX) is tested and stable on that platform for the workflows that matter.
The Actual Conclusion
Linux replaced Windows for everything that runs permanently, serves production workloads, handles infrastructure, and runs development environments.
Windows runs where the gaming ecosystem demands it and where specific tool compatibility requires it.
Both of these things are true simultaneously. The choice isn’t religious. It’s functional. Linux is genuinely superior for server workloads, development environments, and infrastructure — the evidence is that it runs most of the world’s servers, every Android device, and every supercomputer on the planet. Windows is genuinely superior for gaming compatibility and certain desktop application ecosystems — the evidence is that most games are still built for it first.
Use the right tool for the job. Learn both. Understand what each one is actually better at.
That’s been my position since a 386 and a copy of Slackware. It hasn’t changed.
King Frost — TrojanHQ
Next in this section: Distro deep dives, the Thermalright LCD display Linux driver reverse engineering story, and practical Linux setup guides for the TrojanHQ infrastructure stack.