Why I Use Ubuntu
Ubuntu, the Red Hat Ecosystem, and openSUSE: Finding the Balance for Home Infrastructure
When people hear that I settled on Ubuntu across my home lab, servers, and daily workstations, they often assume I must dislike other distributions. That could not be further from the truth.
I genuinely enjoy playing with Fedora, AlmaLinux, and openSUSE. They are fantastic operating systems, and in virtualized environments today, I still spin them up to test workflows and explore their ecosystems.
My journey to Ubuntu wasn't born out of disdain for other distros—it was driven by a very specific set of circumstances during a unique point in Linux desktop history.
A Unique Set of Circumstances
To understand why Ubuntu became my daily driver, you have to look at the constraints I was working with at the time:
- The Wayland & NVIDIA Kepler Transition: Wayland was rolling out by default on cutting-edge distros like Fedora, but open-source Nouveau drivers were not yet viable for my hardware. My laptops were running NVIDIA Kepler cards, which required the legacy 470 driver series. As newer kernels dropped legacy support, those setups broke easily on faster-moving distros.
- Servers on Wi-Fi: Before I had my environment hardwired, my servers had to run over wireless network adapters. Many distros required me to manually compile USB dongle drivers every time the kernel updated.
Ubuntu’s Hardware Enablement (HWE) kernel proved to be the magic bullet. It delivered updated drivers and hardware support directly into a stable LTS base. Eventually, Ubuntu’s kernel just included my Wi-Fi dongle drivers natively out of the box, eliminating the constant manual compiling.
Today, my environment is fully hardwired, hardware support has matured across the board, and I could easily run Fedora, AlmaLinux, or openSUSE on my machines without those legacy roadblocks. But the process of solving those problems taught me the true value of Ubuntu's underlying balance.
The Power of the "Goldilocks Zone": Uniformity Across the Board
In a Red Hat-centric environment, a common best practice is to pair AlmaLinux on the server with Fedora on the workstation.
- AlmaLinux gives you an enterprise-grade, rigorously tested, stable foundation where nothing changes unexpectedly.
- Fedora gives you the modern desktop packages, newer kernels, and fresh software daily-driving demands.
While both use the DNF package manager, they represent two ends of a spectrum: one stays rock-solid and slow, while the other moves quickly toward the bleeding edge. Moving between the two means managing a shift in package availability, driver versions, and software behaviors.
This is where Ubuntu shines. It occupies the Goldilocks middle ground:
- Not Too Old, Not Too New: The LTS base gives you enterprise reliability, while the HWE kernel and backports keep modern hardware running smoothly.
- Total Uniformity: I don't have to keep my servers on an older release while pushing my workstations onto a rapid 6-month upgrade cycle. The exact same base OS, software versions, and repositories run across my desktop workstations, my bare-metal servers, and my Proxmox LXC containers.
- Fewer Surprises: What works on my workstation works identically on my server. I don't have to guess whether a package readily available on my desktop will be missing or restricted on my server.
Red Hat Ecosystem:
[ AlmaLinux (Conservative) ] <--------------> [ Fedora (Bleeding-Edge) ]
Ubuntu Approach: [===== Ubuntu LTS + HWE =====] (Modern, Stable & Uniform)
Comparing the Major Distributions
Here is how the main production-grade distribution families line up when structuring an infrastructure setup:
| Feature / Criteria | Ubuntu / Kubuntu | Fedora + AlmaLinux Ecosystem | openSUSE (Leap / Tumbleweed) |
|---|---|---|---|
| Primary Role | Single unified base for Workstations, Servers, LXCs, and VMs. | Fedora: Modern Workstations. AlmaLinux: Production Servers. |
Tumbleweed: Rolling Workstations. Leap: Stable Enterprise Servers. |
| Release Model | LTS: 2-Year cadence with 5+ years of predictability. Interim: 6-Month option for short-term testing. |
Fedora: Rapid 6-Month release cycle. AlmaLinux: Long-term 10-Year enterprise cycle. |
Tumbleweed: Continuous Rolling. Leap: Regular minor version updates. |
| Kernel & Hardware | HWE Kernel: Backports newer kernels to stable bases for seamless hardware support. | Fedora: Cutting-edge kernels. Alma: Highly stable, conservative enterprise kernels. |
Tumbleweed: Cutting edge. Leap: Conservative enterprise base. |
| Package Management | APT (.deb), native Snap support, simple Flathub/Flatpak configuration. |
DNF (.rpm) unified across desktop and server setups. |
Zypper (.rpm) alongside comprehensive system administration tools. |
| Maintenance | Low: Set it up once, apply security patches, and focus on your applications. | Low (Alma): Set-and-forget. Moderate (Fedora): Requires major version upgrades every 6 to 12 months. |
Moderate: Excellent stability, though major tooling shifts require occasional adjustments. |
Where Does Arch Linux Fit?
Noticeably absent from this comparison is Arch Linux. Having spent three solid years running vanilla Arch on my main laptop, I learned a tremendous amount about system architecture and troubleshooting through that experience.
However, Arch simply does not fit the goals of this platform or my target audience:
- Predictability & Reliability First: When managing self-hosted infrastructure, services, and production workloads, you need a system that works predictably today, tomorrow, and next month. Arch's rolling-release model requires continuous monitoring, manual intervention, and frequent troubleshooting to keep running smoothly.
- Time Management: Fixing broken dependencies, handling upstream updates, or recovering from unexpected manual intervention isn't a substitute for real project development. I prefer channeling my energy into building services—like Nextcloud, virtualization, and automation—rather than maintaining the OS itself.
- Audience Alignment: My goal is to help people build secure, reliable, low-maintenance setups. Recommending a rolling distribution that demands constant system administration overhead runs counter to making tech approachable and predictable.
Conclusion
Every major Linux distribution brings something valuable to the table. OpenSUSE continues to innovate with sleek tooling and robust rollback features; AlmaLinux provides unbeatable enterprise permanence; and Fedora offers one of the cleanest desktop experiences in the ecosystem.
For my infrastructure, Ubuntu simply hit the exact sweet spot I needed. It allows me to spend less time managing OS differences and more time deploying tools that matter.
