this post was submitted on 24 Jul 2026
-20 points (4.5% liked)

Linuxsucks

390 readers
11 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

Game Performance Impressive?

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

🛠️Checking for Linux Hardware Compatibility is Bullshit!

founded 2 years ago
MODERATORS
 

Stability & Release‑Model Terms LiGNUts misuse

  • Bleeding edge: used to mean “latest packages”. Actual meaning: Something too new and untested to be reliable. Arch is cutting edge**, not bleeding edge.**
  • Rolling release: used to mean “always up to date”. Actual meaning: continuous integration of upstream changes, not a guarantee of freshness or stability.
  • Stable: used to mean “reliable”. Actual meaning: frozen, long‑term‑supported, regression‑tested (Debian Stable, RHEL).
  • LTS: used to mean “safer". Actual meaning: supported longer, not necessarily more stable (Ubuntu LTS point releases often ship new kernels).
  • Minimal: used to mean “lightweight". Actual meaning: few packages installed, not necessarily low resource usage.

Security language gets abused to win arguments.

  • Sandboxed: used to mean “runs in a container/flatpak”. Actual meaning: strictly confined with enforced boundaries; many Flatpaks aren’t.
  • Hardened: used to mean “compiled with a few flags”. Actual meaning: system‑wide mitigations, MAC policies, kernel hardening, attack‑surface reduction.
  • Secure: used to mean “not Windows". Actual meaning: threat‑model appropriate protections, not “I don’t get viruses”.
  • Telemetry: used to mean “any network request I don’t like”. Actual meaning: instrumentation data sent for diagnostics, not update checks, CDN hits, or API calls.

Licensing & Ideology Terms LiGNUts misuse

  • Proprietary: used to mean “closed source”. Actual meaning: owned under exclusive rights, which can include open‑source licenses with restrictions.
  • Bloat: used to mean “anything I personally don’t use”. Actual meaning: unnecessary resource consumption, not “has a GUI”.

Software‑Engineering Terms LiGNUts misuse

(These are the funniest because they reveal who has never worked on a large codebase.)

  • Patch: used to mean “workaround”. Actual meaning: a diff applied to source code, not a config tweak.
  • Dependency hell: used to mean “I don’t like this dependency”. Actual meaning: conflicting or unsatisfiable dependency graphs.
  • Lightweight: used to mean “looks simple”. Actual meaning: low CPU/memory footprint, not “has a minimal UI”.
  • Optimized: used to mean “fast on my machine”. Actual meaning: measured performance improvements, not vibes.

Community & Culture Terms LiGNUts misuse

  • Works fine: used to mean “I haven’t hit the bug yet”. Actual meaning: verified functional behavior across contexts.
  • Bug: used to mean “I don’t like this behavior”. Actual meaning: incorrect or unintended behavior according to spec.
you are viewing a single comment's thread
view the rest of the comments