A Linux desktop comes together one layer at a time. Firmware starts the machine. A boot manager selects a kernel. The kernel brings up devices and starts userspace; the init system manages services; a display server or Wayland compositor handles windows and input; the desktop shell adds panels, launchers, settings, and the bits people touch every day.
The layers explain why changing one part rarely replaces everything. Fish can change the command line without changing the compositor. Hyprland and Sway put window layout close to the compositor. GNOME packages a more integrated desktop. Quickshell and Noctalia provide another way to build or configure the shell. Each choice has different defaults, configuration, and failure modes.
Boot changes are the ones to approach carefully. A typo in a panel config is annoying; a bad EFI entry can leave the machine at firmware. systemd-boot’s manual explains its UEFI boot entries. Secure Boot also depends on keys and signed boot artifacts; choosing a bootloader alone does not set up a verified chain.
CachyOS, Arch, Hyprland, Sway, GNOME, Fish, Quickshell, Noctalia, Btrfs, and Limine all appear in the owner’s list of interests. They are separate subjects here, not a claim about one machine’s current setup.
The fun part of Linux desktop customization is how visible the choices become. A compositor decides how windows behave; a shell decides what surrounds them; a launcher changes how applications are found. Keeping a small map of those decisions makes experiments easier to undo and easier to understand later.