Suckless.org: software that sucks less

Political controversy and community culture

  • A substantial part of the thread debates alleged far‑right / neo‑Nazi associations around the Suckless community: torchlit hikes, logo designs overlapping with far‑right imagery, use of terms like “cultural Marxism,” a machine named “Wolfsschanze,” and a revisionist WWII email.
  • One side sees these as consistent dog whistles, argues that Germans/Austrians know the context, and concludes they “wouldn’t touch the project.”
  • Others see the evidence as weak or limited to a few individuals, emphasize traditional non‑political torch walks, or argue that one or two fringe contributors shouldn’t define the whole ecosystem.
  • There’s a broader ethical debate: some refuse to use software tied to ideologies that target them; others insist on separating “art from artist” and focus solely on technical merit.
  • Disagreement also appears over whether communities must expel problematic members vs. “ignore, don’t feed trolls,” and over “woke/identity politics” vs. meritocracy.

Minimalism, configuration, and usability

  • Fans praise dwm/dmenu/st for stability, tiny code, and hackability: editing a few thousand lines of C once, then not touching it for years, is seen as the ultimate “sucks less.”
  • Critics argue minimalism often fails under real‑world workloads, that recompiling for every config change is performative complexity, and that mainstream desktops (GNOME, etc.) better handle random real‑life tasks.
  • There’s back‑and‑forth on whether complexity is “needless” or intrinsic to reality, and whether Suckless’ aggressive attitude (“elitist,” no novice support) is a feature or off‑putting.

Static vs dynamic linking (inspired by Stali)

  • The Stali FAQ leads some commenters to embrace static linking for small in‑house tools, avoiding distro dependency hell and version skew.
  • Others highlight downsides: missed “free” security fixes and bugfixes, brittle static binaries over time, and the value of package managers and shared libraries.
  • Long sub‑thread covers RPATH/$ORIGIN, Nix/Guix, AppImage, Windows’ “DLL next to exe” model, and when static vs dynamic linking is appropriate.

Tools, alternatives, and ecosystem

  • Many mention non‑Suckless tools that embody similar values: zathura, mupdf, Sioyek, SumatraPDF, Okular, AwesomeWM, dwl, Niri, foot, kitty, xterm, and others.
  • Side discussions cover Wayland’s adoption, single‑thread vs multi‑thread designs, and Suckless’ C coding style guide, which some see as arbitrary or inconsistent.