07 The Recommendation

The Paths

Three starting points.

These are not compromise recommendations. They're calibrated to where you are and what you said you want. The quiz on Lesson 05 sent you here.

Path A — The Daily Driver

Debian Testing

+ GNOME or KDE Plasma

"I want something that works. I'll learn as I go."

Debian Testing gives you current software without the instability of Arch's rolling edge
GNOME integrates best with Wayland — pick it for a clean, opinionated experience
KDE Plasma if you want to configure everything — it scales from simple to exhaustive
No Snap packages. No Canonical opinions. A known baseline.
Same apt commands work on any Debian-family system you'll encounter professionally

For you if:

You're new to Linux, want a graphical desktop that works day one, and are willing to learn the terminal over time. Debian Testing is what people who've been doing this for 20 years recommend to friends.

Install guide: Debian Testing →

Path B — The Confident Setup

Arch Linux

+ XFCE or i3 / Sway

"I want to understand every piece of my system."

You install Arch from scratch — you know everything that's on your machine
Rolling release means no version upgrades, no reinstalls — just pacman -Syu
The AUR gives you access to nearly any software ever packaged for Linux
XFCE for a fast, familiar desktop; i3 or Sway if you want keyboard-driven tiling
The Arch Wiki is the best Linux documentation in existence — you'll use it often

For you if:

You're comfortable in a terminal, you enjoy troubleshooting, and you want bleeding-edge software. The install process teaches you more about Linux than six months of Ubuntu would.

Path C — The Performance Builder

Debian Testing
or
Arch Linux

+ XFCE or Fluxbox

"I need every cycle. I don't want the desktop in the way."

XFCE at ~250–400MB RAM — traditional desktop, nothing wasted, everything works
Fluxbox at ~16MB RAM — maximally minimal; built-in window tabs; your toolbar, your choice
Clean base means you know exactly what's running, so you can tune confidently
Gaming: Proton handles most Steam library; install gamemode for CPU/GPU optimization
HPC: Arch especially — you control kernel versions, compile flags, scheduler settings

For you if:

You're building a gaming rig or HPC workstation and need minimal desktop overhead. Do not start with a gaming-focused distro like Nobara — build from a clean base, apply your own tweaks, know what you changed. You'll spend far less time recovering from mystery failures.

Appendix F: Gaming on Linux — drivers, Steam, Proton, gamemode, MangoHUD →

Also Worth Knowing

Ubuntu and Fedora.

These are real options used by real people. They didn't score highest on the learning and transparency criteria — that doesn't make them wrong choices for everyone.

Also Recommended

Ubuntu

The most approachable Linux desktop, by design. Enormous community. Nearly every tutorial you find will be written for Ubuntu. Hardware support is excellent. The installer is graphical and guided.

The honest ceiling: Ubuntu makes choices for you — including defaulting to Snap for several applications. Snap packages are slower to start and served from a Canonical-controlled server. As you grow into Linux, you may find Ubuntu's defaults fighting your preferences. When that day comes, Debian Testing is the natural upgrade path — the skills transfer directly.

Also Recommended

Fedora

Fedora is where new Linux technology lands first. It ships vanilla GNOME, uses Btrfs by default, adopts Wayland aggressively, and is generally ahead of other distros on upstream adoption. Red Hat's backing means serious QA and professional involvement.

The honest ceiling: Shorter support windows (about 13 months per release), smaller community than Debian/Arch, and an ecosystem that doesn't have the same depth as Debian's repositories. A solid choice — especially if you're heading toward RHEL/CentOS in a professional context.

What's Next

After you install.

The course ends here. The journey doesn't. Here's a practical starting order for the first week after your install.

Step 01

Update everything

First action after install — pull every security patch before you do anything else.

sudo apt update && sudo apt upgrade

Step 02

Learn your package manager

Install htop, tldr, and your terminal of choice. Then install things you actually use.

sudo apt install htop tldr

Step 03

Explore /proc and /dev

Run cat /proc/self/maps and ls /dev/. Watch "everything is a file" become real.

ls /proc/$$ /dev/ /sys/class/

Step 04

Learn your dotfiles

Shell config, git aliases, SSH shortcuts, WM keybindings — it's all plain text. See Appendix D.

ls -la ~

Step 05

Read the Arch Wiki

Even if you're not on Arch. It's the best reference for almost every Linux topic.

wiki.archlinux.org

Step 06

Try a different WM

Install a second window manager and switch to it at your next login. You can always switch back.

sudo apt install fluxbox i3

Debian + Fluxbox is a setup worth reading about in depth. The combination is well-documented, proven, and runs lean on everything from a Raspberry Pi to a workstation. A setup guide lives at burnclouds.net → Debian + Fluxbox Setup (2025 Refresh).

Ready to install?

The install guide is next.

If your path leads to Debian Testing — Paths A and C especially — two appendices cover the full journey: the install, and then the post-install setup decisions.

Appendix A

Installing Debian Testing →

Official USB media methods, netinst walkthrough, Forky vs Trixie vs Sid, rolling release benefits, Mesa and kernel graphics support, full codename history.

Appendix B

Debian + Fluxbox: A Real-World Setup →

The opinionated post-install setup. APT guardrails, startx vs display manager, Fluxbox keybindings, PipeWire, the tray stack. Every decision explained.