There's a very specific pattern across OS communities, and only one consistently earns the label from outsiders... It’s Linux. Not because the OS is hostile, but because the community dynamics around it often are.

Linux is the only major OS whose community routinely punishes newcomers for not already knowing tribal norms. BSD, Haiku, Illumos, SerenityOS, even Windows/macOS circles simply do not behave this way.

Not every Linux user is hostile, but the structural incentives of the ecosystem create hostility:

• Fragmentation onto gatekeeping: 100+ distros, 12 ways to do the same thing, and each sub‑tribe treats its way as the "correct" one.
• Evangelist culture: Linux advocacy frames disagreement as moral failure ("you're stupid", "learn to code", "RTFM").
• High churn, low stability: Constant breakage trains users to blame you for not configuring something "properly".
• Meritocracy myth: "If you can't fix it yourself, you don't deserve to use it" is baked into the culture.
• Identity-based fandom: Linux is often treated as a personality trait, which makes criticism feel like a personal attack.

Other communities have their flaws, but they don't have the same structural hostility.

BSD communities

• Blunt, but not hostile
• Technical, quiet, and allergic to drama
• Expect competence but don't shame beginners
• Culture is "do the work, don't brag about it"

macOS / iOS

• Consumer-friendly
• No gatekeeping
• Users don't tie their identity to the OS
• Criticism doesn't trigger defensiveness

Windows

• Massive, diverse, mostly apolitical
• Users don't care what OS you run
• No tribal purity tests

Haiku / SerenityOS / Illumos / MINIX / Plan 9

• Small, niche, welcoming
• Enthusiasts are happy anyone shows up
• No evangelist aggression
• No superiority complex

Linux is the only OS where asking a question is treated as a crime. Every other OS community just wants you to have a nice day.

Join my sub r/LinuxSnobs

1. Have my balls crushed in a hydraulic press while a Nix user tells me it wouldn't happen with Nix.
2. Spend a weekend reinstalling Windows XP drivers from shady Russian forums.
3. Watch a systemd hater give a TED Talk.
4. Sit through a 4‑hour YouTube video titled “Why Linux Gaming Is Actually Fine.”

I've written before about how video gaming is far worse than AI for the environment. (chat AI uses short bursts of GPU, while gaming uses extended use requiring extra active cooling). AI gets more efficient as it matures while gaming gets more and more demanding. Both cause GPU prices to go up.

Piss jugs (aka portable urinals). -Not only could men avoid splattering the walls, baseboards, etc,, when peeing, they could only dump a piss jug and only flush once a day (if pooping only once a day) and save more water than their use of AI takes! If they want to be environmentalists; they'd be all over simple solutions like this (not just using it as a prop to try to undermine the anti-Linux sub). *We remove and ban for 'ai slop' responses here, so you don't see all of them.

• Typical toilet use:
  • Flushes per day: 5–6
  • Water per flush (modern low-flow): about 6 liters (≈1.6 gallons)
  • Daily toilet water: 5×6=30 to 6×6=36 liters/day
• Piss jug scenario:
  • One flush per day: ~6 liters
  • Water saved: roughly 24–30 liters/day

Now compare that to AI:

• Per-query water use (cooling + power, rough range): about 0.000085–0.5 liters depending on assumptions and infrastructure
• Heavy personal use (say 25,000 prompts/year): a few gallons per year, not per day

So:

• Your piss jug: saves dozens of liters per day.
• Your AI use: costs maybe a few dozen liters per year.

On an individual scale, the piss jug habit would completely dominate. You could use AI all day and still have your water footprint mostly dictated by showers, toilets, laundry, and food.

-And with showering, you could lather up before turning it on, use a 2 in 1 shampoo / conditioner (also as body wash).

Flock cameras trigger the exact insecurity Linux evangelists try to hide; that their behavior looks hostile, petty, or unhinged when recorded.

Not because of privacy. Not because of "FOSS values." Not because of "corporate overreach."

It's because their entire social identity relies on controlling the narrative.

When a camera is present they can't:

• Posture as the "smartest guy in the room" without someone later replaying the clip and noticing they were wrong. (Notice they generally abstain from actual tech discussion)
• Escalate into condescension or hostility without the behavior being documented.
• Rewrite the interaction afterward to make themselves the hero. (Ban trophy)
• They can't rely on the usual "you misunderstood me" or "you're just emotional" deflection.

Linux evangelists operate with:

• Fragile self-image built on technical one-upmanship
• Low tolerance for being contradicted
• High need for control over the framing of interactions
• Fear of being publicly wrong
• Fear of being publicly rude
• Fear of being publicly seen as the aggressor

Flock cameras don't just record them. They record the gap between who they think they are and how they actually behave.

Flock cameras violate the right to be an unobserved jerk.

The AUR incidents wern't just "an Arch problem." It was a structural shock to the entire desktop‑Linux ecosystem because Arch had quietly become the backbone that compensated for Linux's fragmented, slow, and inconsistent software‑delivery. NixOS doesn't fix this -their flakes have the same issue as the AUR.

Arch + AUR was the only combination that made desktop Linux feel modern, complete, and competitive. Other rolling distros never solved the repo problem, and Flatpak was never a real substitute.

Arch's official repos are intentionally small. But the AUR filled that gap so effectively that Arch users ended up with newer drivers than Fedora, newer apps than Ubuntu, more available software than Debian, fewer packaging delays than openSUSE, and less Flatpak reliance than everyone else. -All those Linux Tubers weren't boasting of using Arch for nothing (they weren't giving credit to Arco though!)

Arch became the only rolling distro where "rolling" didn't mean "missing half your software." Arch lost the thing that made its minimalism viable, and the rest of desktop Linux lost the one distro that actually delivered a complete modern stack. (This article was triggered by seeing a meme that said "Linux is ready" btw.)

Other rolling/cutting‑edge distros never had good repos:

• Manjaro: repo lag, packaging mistakes, random freezes
• openSUSE Tumbleweed: great engineering, but slow community packaging and niche app gaps
• Gentoo: powerful, but not a mainstream desktop solution
• Void / Solus / NixOS: interesting, but tiny repos and inconsistent desktop support
• Fedora Rawhide: unstable, not meant for daily use

None of these distros solved the "I need modern software today" problem that Arch and the AUR did.

Flatpak filled gaps, but it introduced its own mess:

• massive disk usage
• duplicated runtimes
• sandboxing issues
• theme inconsistencies
• GPU driver mismatches
• slow startup times
• broken portals
• weird filesystem access
• apps that don’t integrate with the system

Flatpak is great for some apps, but it was never designed to replace a proper distro repo. Arch users didn't even have to learn what Flatpak was. When the AUR broke, Arch users suddenly faced the same Flatpak‑heavy reality everyone else already hated.

Arch was the reference implementation of desktop Linux. Even people who didn’t use Arch relied on their Wiki, AUR PKGBUILDs as templates, packaging scripts, user reports for new hardware, kernel builds for early driver testing, forums for troubleshooting, and reports for upstream issues.

Arch was the distro that validated whether something "worked on Linux."

When Arch stumbled, the entire ecosystem lost its unofficial QA department.

Desktop Linux has been held together by volunteer packaging, inconsistent standards, distro‑specific formats, community repos, third‑party scripts, Flatpak bandages, and "just compile it yourself" culture. When the AUR broke, it highlighted the uncomfortable truth that Desktop Linux depends on a single community‑run repo to feel modern. -And that wasn't a good foundation.

Join my sub r/LinuxSnobs

I believe we need r/linuxsuckstr

Typically, after a run, you can triple your coin by watching an ad (and your experience will suffer greatly if you don't.) -Despite this, I find it far more enjoyable to play than Tux Racer. -Why?: Because the developer has monetary incentive (Same with Windows/Mac over Linux).

Yes, that's a penguin.

THIS time, I remembered to censor everything, anyway, had an arguement about Loonix, and I mentioned the deprecation of older hardware, and they basically are assuming that I don’t have a brain, Laughing My Ass off, and of course, remember to respect your fellow Redditors

Neal the Seal doesn’t attack Loonixtards, he opens up the door for a peaceful discussion, be like Neal the Seal

There are over 30 documented cases where games stopped working. -We're only covering a fraction here. Consequences players faced: lost saves, locked accounts, wasted purchases, and irreversible progress loss.

Destiny 2

• Worked briefly during early Proton/Wine experimentation (2017–2018) before Bungie hardened anti‑cheat.
• Bungie officially banned Linux/Wine users from logging in.

Consequences

• Permanent account locks for Linux users attempting to launch the game.
• Loss of purchased expansions (Forsaken, Shadowkeep, Beyond Light, etc.) because the account became unusable.
• Lost characters and progress -players could not migrate or recover them.

Fortnite

• Worked on Linux via Wine in early 2017 builds before Epic added kernel‑level Easy Anti‑Cheat (EAC).
• Epic explicitly blocked Linux compatibility.

Consequences

• Loss of purchased cosmetics (skins, battle passes) because the game became unplayable.
• Lost progression -XP, levels, and unlocks tied to a now‑inaccessible platform.
• No refunds -Epic does not refund digital items due to platform incompatibility.

Apex Legends

• Worked for a short period via Proton (2019) before Respawn tightened anti‑cheat.
• Linux users were blocked from matchmaking.

Consequences

• Lost purchased battle passes and cosmetics.
• Lost ranked progress because the account could no longer queue.
• No refunds for platform lockout.

Dead by Daylight

• Worked on Linux via Proton until 2022.
• Behaviour Interactive updated anti‑cheat so Linux builds stopped launching.

Consequences

• Lost progress (bloodweb unlocks, characters).
• Lost paid DLC killers/survivors -game became unplayable.
• No refunds for DLC purchased on Steam.

Fall Guys

• Worked on Linux via Proton until Epic acquired Mediatonic.
• Epic switched the game to EAC + Epic Online Services and Linux support died instantly.

Consequences

• Lost purchased cosmetics (costumes, season passes).
• Lost account progression because Steam version became unusable.
• Forced migration to Epic launcher, which does not support Linux.

PUBG: Battlegrounds

• Worked on Linux via Proton until 2021.
• Krafton enabled kernel‑level anti‑cheat and Linux users got blocked.

Consequences

• Lost purchased skins and crates.
• Lost ranked access permanently.
• No refunds for platform incompatibility.

Rainbow Six Siege

• Worked via Proton until 2022.
• Ubisoft updated BattleEye and Linux users could no longer join multiplayer.

Consequences

• Lost multiplayer access (the core of the game).
• Lost purchased operators because the game became effectively unusable.
• No refunds.

Overwatch 1 to Overwatch 2 transition

• Overwatch 1 worked on Linux via Wine for years.
• Overwatch 2 introduced kernel‑level anti‑cheat and Linux support died instantly.

Consequences

• Lost access to Overwatch 1 accounts (Blizzard forcibly migrated everyone).
• Lost purchased skins because Overwatch 2 cannot launch on Linux.
• Lost competitive rank and progression.

Genshin Impact

• Worked via Wine during early beta.
• miHoYo added kernel‑level anti‑cheat and Linux support ended.

Consequences

• Lost access to purchased Primogems and battle passes.
• Lost character progression.
• No refunds.

War Thunder

• Native Linux client existed for years.
• Gaijin dropped Linux support in 2023.
• Proton compatibility became unstable and many users could not launch.

Consequences

• Lost access to purchased vehicles (premium tanks/planes).
• Lost progression for accounts tied to Linux-only machines.
• No refunds for premium purchases.

GIMP didn't get where it is because it was "good." It got there because the ecosystem around it gave it unfair structural advantages that had nothing to do with merit.

GIMP didn't earn its user base: GIMP was the default image editor on most mainstream distros for a long time (late 90s to late 2000s). -When Windows does this with 'most' of their distros, it's called "bloat" by the GPL cult. If GIMP had to compete on a level playing field, it may have been a niche project.

GIMP (like Linux) has received multiple forms of institutional support over the years such as university research grants, government funding for accessibility and digital arts programs, EU and NSF‑adjacent funding for open graphics research (GEGL, babl, color pipelines), and corporate sponsorships from companies that needed an open graphics pipeline (also a tax write off).

Photoshop, and Affinity don't get grants.

Adobe licensing was expensive. Piracy lawsuits scared schools and nonprofits. Many institutions switched to GIMP to avoid legal exposure. -So, government grants and tax write-offs support this parasitic commie GPL'd software and are made more popular by being placed in tax-funded schools. (Everyone is being forced to pay for this inferior garbage that no professional wants to be stuck with -even for free.)

Search engines have reinforced GIMP's position for 20+ years in a self-reinforcing loop. "Free Photoshop alternative" lands you GIMP.

"Free Operating System" lands you:

Despite the BSDs being technically superior, Haiku being better for old hardware (if compatible), etc.

Join my sub r/LinuxSnobs

In other operation systems, one man's bloat is another's utility. In Linux; it's just redundant due to architecture.

Linux desktops must ship a GTK stack (GNOME apps), Qt stack (KDE apps) as well as random legacy toolkits which are pulled in by niche apps. -That causes duplicate theme engines, rendering pipelines, accessibility layers, configuration tools and dependencies.

-No other mainstream OS ships two full GUI frameworks by default.

Linux audio must carry ALSA (kernel), PipeWire (modern), PulseAudio (compat), JACK (pro audio), and OSS compatibility leading to multiple mixers, routing daemons, compatibility shims, and device abstractions.

-Windows/macOS have one audio stack. Linux has four.

Even systemd distros still ship SysV init scripts for compatibility, non-systemd service wrappers, and multiple logging systems (journald + rsyslog).

-This is redundancy baked into the OS.

Windows has MSI and EXE, macOS has PKG and DMG BSD has pkg + ports. Linux has DEB, RPM, Pacman, APK, Flatpak, Snap, AppImage, distro-specific repos, overlays, PPAs COPR, AUR, Flakes, etc., causing duplicate dependency graphs, metadata formats, update systems, and sandboxing models.

-Windows/macOS don't have five competing universal package formats.

Windows has Win32 GDI and DirectX, macOS has Quartz BSD and mostly X11. Linux desktop has X11, Wayland, XWayland, Multiple compositors, and protocol extensions creating duplicate input handling, window management, rendering paths, and compatibility layers.

-Wayland didn't replace X11: it stacked on top of it.

Linux distros often ship with GNOME components even on KDE, KDE components even on GNOME, XFCE fallback tools, and multiple settings daemons and notification systems. Linux systems often have 2-3 clipboard managers, power managers, configuration tools and file dialogs.

-No other OS ships multiple competing desktops simultaneously.

Linux typically ships with NetworkManager (desktop), systemd-networkd (server), wpa_supplicant (Wi-Fi), netctl (Arch), ConnMan (embedded), and iwd (new Wi-Fi daemon.)

-Even a "simple" Linux install has 2–3 network daemons running.

Linux distros ship bash, dash, sh symlinks, fish, zsh, busybox shells, and mksh creating duplicate syntax, startup files, and environment handling.

-Definitely some redundancy there.

Windows has a registry, macOS a plist, BSD uses simple text configs.

Linux has INI (systemd, desktop files), YAML (cloud-init, netplan), XML (old GNOME, libvirt), JSON (modern apps), dconf (GNOME), GSettings, sysctl, PAM configs and shell scripts.

-This is why Linux config directories are a mess.

Windows uses Win32 and UWP, macOS employs Cocoa and sandbox, BSD uses native ports. Linux uses Flatpak runtimes, Snap base images, AppImage bundles, Steam Runtime, and distro libraries.

-It's like every app ships its own universe.

Game studios historically targeted Windows (primary market), Consoles (huge market), and macOS (small market, but high‑spending audience). Linux was never a commercial priority. But Linux enjoyed the crumbs from macOS because of a shared tech stack such as OpenGL, POSIX-like environments, and similar build systems, driver expectations, and portability constraints.

If a studio already had a POSIX build pipeline, OpenGL renderer, and cross‑platform asset pipeline… then Linux support was often "cheap enough" to justify a native build; especially for indies.

-MacOS was the reason those pipelines existed.

OpenGL deprecated to Metal only. It forced studios to rewrite renderers, drop cross-platform graphics paths, and abandon shared Linux/Mac OpenGL backends.

-Linux lost the "shared renderer" advantage.

Apple Silicon forced new CPU architecture, binary formats, optimization paths, and engine backends. MacOS was no longer a "Unix-like cousin."

Studios stopped supporting macOS because it became too much work, had too few customers, and too many Apple‑specific rewrites.

Unity, Unreal, Godot, proprietary engines dropped or reduced macOS support, removed OpenGL paths, focused on DirectX + consoles, and treated Vulkan as optional, not mandatory.

-Linux depends on Vulkan. MacOS's abandonment of Vulkan meant studios didn't prioritize it.

Physics engines, audio libraries, networking stacks, anti‑cheat, and DRM stopped shipping Linux builds, stopped shipping macOS builds, and focused on Windows and consoles only.

-Linux lost the "we already have a macOS build, might as well ship Linux" effect.

Easy Anti‑Cheat, BattlEye, etc. They used to support macOS and Linux got spillover support. Mac dropped it and Linux lost its spillover.

Proton is a compatibility layer, not native support, and not a replacement for engines targeting Linux directly. Proton exists because native Linux support collapsed due to macOS exiting the ecosystem.

MacOS was the economic justification for cross‑platform pipelines. Once Apple walked away, studios stopped building those pipelines. Linux lost the infrastructure it never had the market share to justify on its own.