IceWM

IceWM, a lightweight X11 window manager dating back to the late 1990s, prompts both nostalgia and renewed interest from users who value speed, low resource usage and minimal configuration over modern, feature-heavy desktop environments. Commenters compare it to alternatives like AwesomeWM, Fluxbox, Xfce and tiling managers, often describing a personal trajectory from heavy desktops toward simpler setups that “stay out of the way.” The thread also broadens into a debate over X11 versus Wayland, GUI toolkits such as GTK and Qt, and how design choices in contemporary Linux desktops affect usability, stability and long-term compatibility.

IceWM’s Role and Use Cases

  • Many reminisce about using IceWM in the early 2000s; it was valued for speed and tiny resource usage on weak hardware.
  • Several people still use it today: as the main WM for audio work, on tablets and niche devices, for remote desktops via xrdp/RustDesk, and on “dashboard” or headless-style machines where a simple, integrated panel+menu+WM is ideal.
  • It’s praised for staying out of the way, being scriptable, and working out of the box. Some suggest it as a good environment for kids or for teaching Linux on old machines.
  • Downsides mentioned: configuration is less intuitive than fluxbox, some quirks (e.g., difficulty getting a single workspace), lack of Aero-style snapping, and an old-school UX look unless you tweak themes. Lack of Wayland support is a blocker for some.

Comparisons with Other WMs/DEs

  • Compared to Xfce: IceWM is “just” a window manager, lighter but less feature-rich and less modern as a full desktop.
  • Some users have migrated through IceWM → GNOME 2 → MATE, or to tiling WMs like AwesomeWM, i3, Xmonad, dwm, or to fluxbox/openbox/ctwm/JWM.
  • A recurring pattern: early heavy customization and DE-hopping, later settling on one minimal, consistent setup that demands little attention.

X11 vs Wayland (and Systemd/Pipewire)

  • One camp sees X11 as definitively legacy: praises Wayland, Pipewire, and systemd components as a clean break that yields a more cohesive, polished desktop and leverages modern GPUs well.
  • Another camp argues X11 is still superior or at least necessary: Wayland is described as immature, fragmented, missing scripting APIs, window placement control, some accessibility tools, reliable push-to-talk, robust remote display, and simple, compositor-agnostic configuration.
  • Some think X11 could have been cleaned up rather than replaced; others reference long-standing technical debt as justification for starting over.
  • Systemd and Pipewire provoke similar division: some see coherence and reduced tinkering; others see overreach, invasive behavior, and Linux audio still being messy.

GNOME/GTK, KDE, and Alternatives

  • Strong criticism of GNOME/GTK’s “opinionated” and frequently changing UX, removal of features, and reluctance to support things like server-side decorations; some claim it drives newcomers away.
  • Others report GNOME 3 working well for non-technical users, especially those familiar with mobile-like interfaces.
  • KDE/Qt is seen by some as powerful but heavy and legacy-laden; others say it has improved a lot.
  • There is interest in alternative toolkits/desktops (e.g., BeOS/Haiku-derived V OS) and in the idea of a new, less encumbered GUI stack.