Lesson 06

Your
Desktop

The desktop is not the operating system. It's a layer of software you run on top of one. You can replace it, swap components, or run multiple setups side by side. This lesson helps you find the one that fits how you work.

3 sections
Tabs inside
~15 min read

"Am I right that there are multiple layers — like, clicking the Slack icon isn't just opening Slack?"
Yes. Exactly right. Clicking Slack on KDE means: KDE receives your click, routes it through the window manager, which tells the display server, which asks the init system to launch the process, which is scheduled by the kernel, which asks the hardware for CPU time. That's five layers before Slack draws a single pixel. A minimal setup (Fluxbox + no DE) removes two or three of those layers — fewer things to configure, fewer things to break, less RAM sitting idle. Swapping any layer is usually straightforward. Changing the distro is the hard one.

Section 01

Desktop Environments

A desktop environment is a bundled collection: window manager, file manager, settings app, notification daemon, app launcher, system tray. They're designed to work together as a unit. The convenience trade-off: you get less say about any individual piece.

Select a desktop environment

Desktop Environment
GNOME
The most opinionated DE on this list. GNOME has a vision — a tablet-influenced, activity-based workflow — and it executes that vision consistently. Extensions can modify almost anything, but vanilla GNOME expects you to use it on its terms. On Wayland, GNOME is the most stable and well-integrated option available.
GTK4 Wayland-native Mutter WM GDM login
Who it's for
The pragmatist.
You want a polished, consistent desktop that looks like it was designed by someone. You're willing to learn GNOME's workflow instead of forcing it to match Windows. Fedora ships vanilla GNOME — arguably the best place to run it.
Recommended on Fedora Extensions available
Desktop Environment
KDE Plasma
KDE is so feature-rich it barely counts as just a desktop environment — it's practically its own operating system. Every visual element, every behavior, every keyboard shortcut is configurable to a degree that borders on overwhelming. Qt-based. Genuinely impressive technical work. Lighter than it looks; heavier than everything else here.
Qt6 Wayland + X11 KWin WM SDDM login Maximally configurable
One thing to know
KDE Wallet.
KDE's credential management system may prompt you at login to unlock a "wallet" for stored passwords and secrets. This can surprise new users — it's not a virus, it's not a bug, it's KDE's keyring equivalent to GNOME Keyring. You can configure it to auto-unlock, or disable it if you don't use KDE apps that store credentials.
kwallet-pam for auto-unlock
Desktop Environment · Recommended
XFCE
XFCE is the right answer for a large proportion of Linux users. Traditional desktop metaphor (taskbar, icons, right-click menus), low RAM footprint (~250–400MB), fast, stable, and mature. Nothing surprising. Everything configurable. It's the practical choice when you want a real desktop without DE bloat.
GTK3 X11 primary (Wayland progressing) Xfwm4 WM ~250MB RAM
Why XFCE for starters
Familiar + honest.
If you're coming from Windows, XFCE will feel immediately familiar: taskbar at the bottom, start-button-style menu, draggable windows. The small overhead over a bare window manager is worth it while you're learning — things like battery meters, volume controls, and display settings just work without manual setup.
Best starter minimal DE Gaming-friendly overhead

Section 02

Window Managers

A window manager without a desktop environment. No bundled file manager, no settings daemon, no notification system running by default — but none of those things are gone. You choose what to add. The fastest and most customizable Linux setups look exactly like this: deliberate, not sparse.

Blackbox 1997 · C++
Fluxbox 2001 · fork
Openbox 2002 · rewrite in C
← both forked from Blackbox; Openbox was later fully rewritten

Select a window manager

Window Manager · Daily driver pick
Fluxbox
A C++ fork of Blackbox with a built-in toolbar, slit (dock), and — its signature feature — window tabbing. Multiple windows can share a single frame with tabs across the top. Floating layout, fast, minimal. Uses its own style files for theming. Under 16MB RAM.
X11 ~16MB RAM Floating Tabbed windows
Honest assessment
Best for the patient builder.
XFCE and Fluxbox are the two best minimal setups — equal and opposite. Fluxbox is smaller and more minimal, but that comes with more time spent tweaking. Getting things like a battery meter working takes more deliberate effort than on XFCE. Fluxbox rewards the user who is willing to invest in their setup. If you're not yet sure you want to invest that time, start with XFCE — you can always migrate.
Recommended for starters: XFCE first
Window Manager
Openbox
Started as a Blackbox fork but was completely rewritten in C — it no longer shares Blackbox code. Highly configurable through XML config files. Unlike Fluxbox, Openbox ships with no panel — you add your own with tools like tint2 or fbpanel. This makes it more extensible but requires more initial setup. It integrates cleanly as the WM for LXDE.
X11 ~7MB RAM Floating XML config
vs Fluxbox
The trade-off.
Fluxbox: slightly more opinionated, built-in toolbar and tabs, config files easier for beginners. Openbox: lighter (~7MB vs ~16MB), more extensible, no built-in panel means more choices but also more work. Both are valid. Openbox is often used as the WM inside lightweight DEs; Fluxbox is typically used standalone.
Best: standalone or with tint2
Tiling WM · X11
i3
The most popular tiling window manager. Windows tile automatically in a grid — no overlapping, no dragging. Every action has a keyboard shortcut. You stop reaching for the mouse. Fast, logical, learnable. The configuration is a single text file. Once you internalize the tiling model, floating windows feel primitive.
X11 Tiling Keyboard-driven i3bar included
Tiling WM · Wayland
Sway
i3-compatible Wayland compositor. If you want i3's keyboard-driven tiling workflow but on Wayland, Sway is the direct path. Config files are nearly identical to i3's. More actively developed at this point than i3. If you're starting fresh and want a tiling setup, Sway is the better long-term choice.
Wayland i3-compatible config Compositor + WM
Wayland Compositor
Hyprland
Hyprland is a Wayland compositor and WM known for smooth animations, rounded corners, and a highly visual aesthetic. It's the "ricing" WM of choice right now — r/unixporn is full of Hyprland setups. Dynamic tiling. Actively developed. The community is large and produces compelling screenshots.
Wayland Dynamic tiling Animations High ricing potential
Honest note
Try it. You can always switch.
Wayland has made significant stability progress in the last 3–5 years. Coverage gaps remain — especially for gaming, screen capture, and remote desktop — but they're narrowing. Hyprland specifically is under active development, which means occasional breakage with updates. It's worth trying. If it doesn't work for your use case, switching WMs or display servers is one of the easier changes you can make on Linux.
Gaming gaps remain Can coexist with X11
Window Manager
Ratpoison
Ratpoison barely counts as a window manager in the conventional sense. No mouse support — by design. No title bars. No desktop. Interface is entirely keyboard-driven and modeled on GNU Screen. You use key chords to split the screen, switch windows, and run commands. It is the most minimal functional window manager in existence.
X11 No mouse GNU Screen model <3MB RAM
Who this is for
You know who you are.
To use Ratpoison, you would need to actively not want a window manager in any conventional sense, and be comfortable enough with the terminal that graphical window management feels like overhead. This is not a starter WM. It's a statement. If you're reading this course for the first time, come back to Ratpoison in a year.
Not for beginners GNU Screen fans

WM without a DE — what does that actually look like?

A WM-only setup doesn't mean a stripped-down experience. It means you chose every piece that's running — nothing more, nothing less. No functionality is missing. Bloat is.

On a Debian + Fluxbox machine with no display manager, login looks like this: you get a terminal prompt. Type startx and .xinitrc launches Fluxbox. You're in a full graphical session. No GNOME. No KDE. No XFCE. Nothing running in the background that you didn't put there.

What the WM handles

  • Window placement and focus
  • Resize, move, minimize
  • Keyboard shortcuts
  • Right-click root menu (app launcher)
  • Built-in toolbar / taskbar (Fluxbox)
  • Window tabbing (Fluxbox)

What you add, if you want it

  • File manager — Thunar, PCManFM, or just the terminal
  • Notifications — dunst (lightweight daemon)
  • Status bar — Fluxbox's is built in; others add polybar or tint2
  • Login screen — a display manager like LightDM, or skip it and use startx
  • Compositor — picom (shadows, transparency) if you want it

A DE bundles all of this for you — one decision, one package. A WM setup lets you pick each piece independently. Both approaches give you a fully functional graphical environment. The difference is whether someone else decided the stack, or you did.

EDITORIAL NOTE

XFCE and Fluxbox are the two best minimal setups — equal and opposite sides of the minimal/functional comparison. Fluxbox is smaller and more minimal, but that also means more time tweaking to get things like a battery meter working. XFCE's small amount of extra overhead is exactly why it's the recommendation for starters over Fluxbox. That said: Fluxbox is a daily driver worth returning to once you know what you're doing. You can also install multiple window managers simultaneously and switch at login — try them. The distro is the hard commitment, not the WM.

Section 03

X11 vs Wayland

You will choose one when you log in. Most display managers let you select at the login screen. Here is what you are actually choosing.

Display Protocol
X11 / Xorg
The original. In continuous development since 1987, with the X.Org server actively maintained, cared for, and fed — do not believe the obituaries. Excellent compatibility: gaming, screen capture, remote desktop, recording, streaming all work without qualification. The vast majority of WMs and DEs still target X11 first.
Best gaming compatibility Screen capture / OBS Remote desktop Supported by all WMs
Display Protocol · Newer
Wayland
A newer protocol with better security (applications cannot spy on each other's windows or keystrokes), better GPU integration, and a cleaner design. GNOME and KDE on Wayland are both mature and worth using. Coverage gaps remain for gaming pipelines, screen capture in some compositors, and remote desktop — but these are narrowing every year.
Better security model GNOME native Sway, Hyprland Some gaming gaps remain

Practical recommendation: If you're on GNOME or KDE, use Wayland — it's stable and well-integrated. If you're on XFCE, Fluxbox, i3, or any other traditional WM, use X11 for now. If you're gaming, use X11 until you've confirmed your specific games and capture tools work on Wayland. You can check with echo $XDG_SESSION_TYPE at any time.