I run two completely different Linux distributions and I don't think about it much anymore. On my desktop it's Arch. On my server it's Debian. They have almost nothing in common, which is the point. It's the sanest setup I've found in thirty years of doing this.
But people ask about it, and since this site is partly notes to my future self, here's why.
The desktop is mine. It's where I work, play, think, and occasionally break things on purpose to see how they work. I want it exactly the way I want it, and I don't want anything I didn't ask for.
I run Hyprland on Wayland. Tiling window manager. No desktop environment. No panel unless I put one there. No notification system unless I configure one. No file manager, no settings app, no "getting started" wizard. Just a blank screen and a terminal and thirty years of opinions about how a computer should behave.
People hear "Arch" and think it's about difficulty. It's not. The installation is a weekend project the first time and half an hour every time after that. The point isn't that it's hard. The point is that nothing happens unless you make it happen. Every package on my system is there because I chose it. Every service running is one I started. Every config file is one I wrote or edited. There is no mystery process eating CPU in the background. There is no update that rearranges my workflow overnight.
The rolling release model means I'm always on the latest kernel, the latest drivers, the latest mesa. That matters when you're running games on hardware that the rest of the world wrote off three years ago. Proton and Wine are moving fast. Vulkan support is moving fast. The gap between "runs on Linux" and "runs well on Linux" gets smaller every month, and being on a rolling release means I'm riding that wave instead of waiting eighteen months for the next point release to catch up.
I've run Skyrim, Baldur's Gate 3, Fallout: New Vegas with a full mod stack, and Elite Dangerous on this setup. On hardware that would make a Windows gamer wince. It works because the system isn't wasting resources on anything I didn't ask for.
And yes, I use Arch btw.
The server is not mine. I mean, I pay for it. I maintain it. I configured every service on it. But it doesn't exist for me. It exists to serve pages to strangers on the internet, reliably, at three in the morning, while I'm asleep. It has a different job and it needs a different temperament.
Debian stable is boring. That's the entire sales pitch. Packages are old. Updates are infrequent. New features arrive sometime between "eventually" and "when they're ready." Nothing breaks because nothing changes. The kernel is ancient by Arch standards. The version of Nginx is a few minors behind. None of that matters. What matters is that it starts, it runs, and it stays running.
How long does it stay running? Here's one of my servers:
root@salsa-vpn:~# uptime
21:49:24 up 532 days, 3:58, 1 user, load average: 0.00, 0.00, 0.00532 days. Zero load. One user (me, checking on it). A year and a half of serving pages without a restart, a crash, or a late-night emergency. That's just Debian doing what Debian does.
This site, lethio.com, runs on a Hetzner CPX11. Two virtual CPUs, two gigs of RAM, Debian 12. It serves static HTML over Nginx with TLS from Let's Encrypt. The server's job is to be invisible. When I don't think about it for months at a time, that means it's working.
I could run Arch on the server. I have the skills. I'd also have the 3am pages when a rolling update breaks something that was working fine. The server doesn't need the latest kernel. It doesn't need bleeding edge mesa. It needs to serve files and not fall over. Debian does that better than anything else because Debian doesn't try to be exciting.
There's a mindset in tech that you should standardise everything. Pick one distro, one workflow, one set of tools, and use them everywhere. Easier to maintain, or so the argument goes.
That's corporate thinking. It makes sense when you're managing a fleet of servers and a team of people who need to be interchangeable. It makes no sense when you're one person running a desktop and a VPS. Different jobs need different tools. A surgeon doesn't use a scalpel to chop onions.
The desktop is a workshop. I want sharp tools, the latest everything, and the freedom to rearrange it on a Tuesday afternoon because I felt like it. The server is plumbing. I want it to work and I want to never think about it.
What they have in common is that both are minimal, both run exactly what I told them to run, and neither phones home or collects telemetry or asks me to agree to anything. They're just Linux. They do what I say.
Yes, some online games don't work on Linux because their anti-cheat systems require a level of kernel access that Proton can't provide. Valorant, for example. Some competitive multiplayer titles with invasive ring-zero anti-cheat will refuse to launch.
I'm in my fifties. I don't play Valorant. I play single-player RPGs with mod lists longer than most people's Steam libraries. I play space sims. I play roguelikes. The anti-cheat holdouts are a non-issue for the kind of gaming I actually do, and I suspect that's true for more people than the discourse suggests.
If you're twenty and competitive Fortnite is your life, sure, Linux is a compromise there. But if you're the kind of person who mods Skyrim for six hours before playing for one, or who's deep in a Fallout: New Vegas playthrough with a mod collection that would make Todd Howard cry, Linux isn't a compromise at all. It's better. Lighter system overhead means more headroom for the game. Latest Proton means better compatibility than you'd expect. And no Windows Update will ever restart your machine mid-session.
This isn't really about Arch vs Debian. It's about using the right tool for the job and knowing what your computer is actually doing. Most people run whatever came preinstalled and never question it, which is fine. I'm not most people.
I want a desktop that's fast and entirely under my control, and a server that's still running in 532 days without anyone touching it. Both are free. You just have to care enough to set them up.
If you care, the Arch Wiki is the best documentation project on the internet regardless of what distro you run, and Debian's docs will walk you through everything else. Between the two of them, there is no question about Linux that doesn't have an answer.
My desktop has sawdust on it and sharp edges everywhere. My server is a sealed box I haven't logged into in months. They're both exactly what I need them to be.