this post was submitted on 16 Aug 2026
-2 points (33.3% liked)

Linuxsucks

398 readers
53 users here now

For knowledge and awareness about what using Linux is really like and pointing at its cultish toxic community. We also cover FOSS /FLOSS failures, and issues with GPL since it relates to Linux. Moderation is heavy handed to appeal to our target users.

Rules:

  1. FOSS (especially GPL) advocates and Linux (specifically GNU/Linux) evangelists aren't welcome (GNU Hurd will count as Linux). -We ask that you block us and we will perma-ban for violations of this rule.
  2. Try to stay on topic (that is LINUXSUCKS!). No bashing other OSs or each other. We aim for a cohesive non-toxic community with the interest of cautioning people / would be victims from Linux. At our discretion, we will remove what we consider pollution.
  3. Moderators run the sub, not the users. It's not democratic, and we don't care how you think it should be run. -Feel free to make and run your own community.
  4. "Not your Billboard" -Over-represented companies will have positive posts removed and appropriate bans may be issued. -Those companies included so far will be Valve/Steam/Proton, Google, and Brave (browser).

⚠️Collection of Articles

⚠️Linux/FOSS can damage hardware or firmware

🪤Linux Community Advice Breaks Windows

🫃Mixing Apps Bloats LiGNUx

😎Linux running servers isn't a brag

👾Is Linux Running Games Near Windows Performance Impressive?

🚮Wasted Ram on Different Toolkits and Distro-Agnostic Packages in Linux

🛰️Critical ISS Systems do NOT run Linux

⚠️Abandoned Software is Dangerous (and common on Linux)

🧻FOSS Devs Quit and Sellout on Unappreciative Userbase

⚠️Firmware Flashing is Riskier on Linux

💊Linux Community Toxicity Ties Directly into Inferiority Complex Psychology

👍The Positives of Telemetry

👾Failures of Proton

⚠️How Linux Stores Browser Passwords is a Security Issue

💊The Psychology of Conspiracy Thinking

🤬Rabid LiGNUxers Ignorantly Get Angry at Devs

😳Does Linux Dominate SuperComputers? -Yeah, but So What!

😎Linux Myths Compilation

⛪The Linux Cult - Religious Parallels

😎Before Wayland: “Linux is secure, Windows is insecure.” -(Selective Dishonesty)

⏳Why Wayland is Taking so Long

😎Major Desktop Applications Missing on Linux

⚠️Sudoedit vs Edit as Root

😎Linux is NOT Great for Developers

😎Kernel Level Anti-Cheat is fine!

⚠️The Privacy / Security Paradox

⚠️Linux Storing Passwords as Plain Text

😎How to Continue Using Unsupported Windows Online on Old Hardware

😎Don't Trust Desktop Marketshare

💊Piracy is Less Harmful than GPL

😎The Most Influential Formerly‑Proprietary Projects that Became Important to Linux

🤬GNU Holds Linux Back (Directly)

💊It is Linux Fault -Why OEMs, Apps Don't Support Linux

🔐 Secure Boot + TPM 2 vs. Linux Alternatives

🛠️Checking for Linux Hardware Compatibility is Bullshit!

🤪Distro-Hopping Madness!

⚠️The Myth of Linux Security

👾Linux Gaming: The Roast It Has Earned

💊 Linux is Better for Old Computers?

💊Linux Sucks at its Core

💊Lies told about BSD to retain support of cult

💊FOSS Apps Run Better on Win/Mac

🤪Isolation is Dangerous!

💊Linux Sucks -Even the Kernel

😎Haiku for Older Hardware

founded 2 years ago
MODERATORS
 

The Unix philosophy encourages tiny, composable tools, and Linux distributions preserve decades of legacy commands. There are multiple commands that do the same job, often with identical flags, sometimes with wildly different syntax, all coexisting forever because nothing can be deprecated. Linux inherits 50 years of overlapping tools, and nobody has the authority to remove any of them.

You get three ways to list files, four ways to print text, five ways to search, six ways to edit streams, and ten ways to check system info; all valid, all canonical, all mutually incompatible.

Multiple commands for the same basic action

  • List files: ls, find, stat, tree, exa, fd
  • Print text: echo, printf, cat, sed -n, awk '{print}'
  • Copy files: cp, rsync, install, dd, tar cf - | tar xf -
  • Move files: mv, rsync --remove-source-files, rename, mmv
  • Delete files: rm, unlink, find -delete, shred, wipe

Redundant text-processing tools

  • grep — search text
  • egrep — grep with extended regex
  • fgrep — grep without regex
  • awk — search + print + transform
  • sed — search + replace + stream edit
  • perl -ne — search + replace + scripting
  • ripgrep (rg) — grep but faster
  • ag — grep but faster before ripgrep
  • ack — grep but for developers
  • find + grep — grep but worse
  • grep -R — find but worse

All of these can search text. All of these have different syntax. All of these are still installed.

Redundant file search commands

  • find
  • locate
  • whereis
  • which
  • type
  • command -v
  • fd
  • ripgrep (yes, people use it as a file finder)

Each solves a slightly different problem, but users treat them interchangeably.

Redundant system information commands

  • Disk usage: df, du, ls -lh, stat, ncdu, dust
  • Processes: ps, top, htop, atop, glances
  • Network: ifconfig, ip, ss, netstat, nmcli, iw, iwconfig
  • Hardware: lspci, lsusb, lsblk, blkid, inxi

Redundant package management

  • apt, apt-get, apt-cache, dpkg
  • yum, dnf, rpm
  • pacman, yay, paru
  • snap, flatpak, appimage

This isn’t just redundancy; it's fragmentation masquerading as choice.

Redundant scripting constructs

  • Conditionals: [ ], [[ ]], test, (( ))
  • Subshells: $( ), ```
  • Variable assignment: var=value, declare, typeset, local
  • Loops: for, while, until, seq | while read, xargs -n1

Half of these exist because Bash absorbed features from:

  • sh
  • ksh
  • zsh
  • POSIX
  • GNU extensions

-And never removed anything!

No central authority is why! Nobody can say "this command is deprecated." So, nothing ever dies. Even if they could, a lot of these may be Rust-rewrites with BSD or MIT license that the cult objects to. GNU Holds Linux Back (Directly)

Every few years someone writes grep but faster, ls but prettier, find but sane, and cat but with syntax highlighting. Debian, Arch, Fedora, Alpine; all ship different defaults.

Linux doesn’t have one way to do things; it has every way except the simple one.

you are viewing a single comment's thread
view the rest of the comments