Sorry, no TLDR for this one. Loonixtards skip over all this with ignorant statements like "Just use Bazzite" -or whatever shitty distro is least shit on atm, and the differences deserve a closer look. (Even though it's still Linux and still shitty)

Feature, and compatibility (drivers), update more frequently and sooner (rolling release) resulting in more frequent and random but minor breakages. Rolling release supports newer hardware and features that people with not so old hardware might prefer.

Point‑release distros give you predictability and staleness.

With rolling you should update at least weekly (something people using SDD with limited writes might consider excessive). -Wait longer and you're taking bigger risks.

What some call "stable", I prefer to call "point release". They're only "stable" (unchanging) for ~ 6months or when you decide to upgrade (2-5 years). Breakages are often more severe on point release upgrades, but you know better when to expect them and don't wake up to a ~10-15-minute fix with 5 minutes to do it in.

Rolling release is safer if you update frequently.
Point release is safer if you update rarely.

People often think rolling is horrible because they update once every 6 months and then blame Arch for exploding. (pebkac)

Is Arch not new user friendly? -Think of it like this: Even seasoned users still follow the guide to install Arch. They still follow the instructions to fix it when it breaks. They don't have to learn flatpak, snap, appimage, or search decade old fixes in an Ubuntu forum for their Debian / Ubuntu based distro. Users are rightly told "RTFM" because literally all the answers are already published in the wiki, streaming sites, etc. If they're not: you're not getting an answer.

Rolling release IF: You want the newest hardware support, DEs, Wayland improvements, game fixes, and kernel features.

Point release IF: you want boring reliability (if reliable from start), minimal surprises (but can handle a huge hurdle down the road *most people likely hop by then), or a system that behaves like an appliance.

Myth: "Immutability makes Linux stable."

It makes the root filesystem stable and does nothing for:

• GPU drivers
• Wayland quirks
• PipeWire regressions
• Kernel bugs
• Desktop environment breakage
• Flatpak sandbox leaks
• Systemd weirdness

Myth "It's more secure."

(Overstated) Security still depends on:

• App sandboxing
• Kernel hardening
• SELinux/AppArmor
• Supply chain integrity
• User behavior

You're not stopping:

• Malicious Flatpaks
• Browser exploits
• Rogue extensions
• Compromised user configs
• Malware running in $HOME

Myth: "It's the future of Linux desktops."

The Linux desktop is built on:

• Customization
• Tinkering
• Package managers
• User‑controlled configs

Immutability counters it.

Myth: "Flatpaks solve everything."

They don't solve:

• GPU driver mismatch
• Kernel ABI issues
• Hardware enablement
• Desktop integration
• System‑level dependencies

Even advanced users have to deal with:

• log analysis
• journalctl
• kernel parameter tweaking
• driver blacklisting
• udev rules
• fstab edits
• permissions debugging
• service restarts
• config file conflicts

Home users should not need to be sysadmins.

But it cannot dominate because:

• Valve doesn't want that responsibility
• OEMs won't ship it
• The Linux ecosystem resists standardization
• The proprietary Steam components prevent true forks
• The desktop market requires enterprise‑grade stability
• The economics don't make sense

It was a pipe dream for some Loonixtards and it shows just how bad off Linux still is and will continue to be.

It's easier to fixate than acknowledge the systemic, multi‑layered mess that actually makes Linux suck, and is often a form of denial that Linux does suck (blame the community -not the OS).

Linux sucks for many reasons, not one big one (other than maybe GPL). -But psychologically, people prefer a simple story (like the community), a clear antagonist (like RedHat), and that helps protect their identity.

They're the tough calls for moderators on linuxsucks101 because they 'can' contribute, but we can see through them that deep down the 'linux sucks' for them is really them trying to improve something they still believe in. -And letting them carry on here leads to feelings of investment and increased bitterness when and if we end up banning them. On the other hand, we hope that they actually read and learn, and don't just vent about their fixation here.

Scapegoating protects the "Linux is good actually" identity

• If the problem is "NVIDIA is evil," then Linux itself stays pure and untainted.
• If the problem is "Wayland isn't ready," then the ecosystem isn't fragmented, it's just in limbo. (but isn't it always)

They avoid the real issue: Linux desktop is a coordination failure.

Actual reasons Linux sucks:

• fractured standards
• duplicated effort
• incompatible APIs
• inconsistent UX
• volunteer labor shortages
• no unified direction
• distro fragmentation
• lack of testing resources
• hardware vendors not caring
• DEs reinventing the wheel
• no stable ABI
• no product owner

Every community has its favorite scapegoat:

• Arch users: “It’s systemd’s fault.”
• Ubuntu users: “It’s GNOME’s fault.”
• Fedora users: “It’s NVIDIA’s fault.”
• r/linux: “It’s Microsoft’s fault.”
• r/linuxmasterrace: “It’s the user’s fault.”
• r/linuxsucks101: “It’s everything’s fault, and also funny.”

These users often hold two conflicting beliefs (cognitive dissonance):

1. "Linux is superior."
2. "Linux breaks constantly."

To resolve the contradiction, they externalize the blame.

Scapegoats are cycled like seasons:

• 2010: PulseAudio
• 2012: GNOME 3
• 2014: systemd
• 2016: NVIDIA
• 2018: Wayland
• 2020: Electron
• 2022: Flatpak
• 2023: PipeWire
• 2024: Snaps
• 2025: “The user”

Anything that needs old DirectX 8/9 with weird shaders

• Custom shader hacks
• Old anti‑cheat
• Old launcher dependencies
• DirectShow video codecs

…can break or require manual fixes.

Windows still wins here because it has:

• Native DX9
• Native DirectShow
• Legacy codec support
• OEM GPU drivers from the era

Linux has to translate everything.

Games tied to old GPU driver behavior

If the game depends on:

• Old Nvidia driver quirks
• Old AMD Terascale behavior
• Old DirectX caps
• Old fixed‑function pipeline hacks

Linux will struggle because Mesa/Nouveau don’t replicate those quirks.

Windows still has the original drivers.

Games that rely on ancient middleware

Examples:

• GameGuard
• PunkBuster
• StarForce
• SecuROM (post‑patch)
• Old .NET versions
• Old Visual C++ runtimes

Linux can run some of these, but not reliably.

Those really old games that "Linux is better for" often run on emulators or gaming websites. When we point out the AAA games that Linux can't play; we're told 'there's plenty of great games we can play'. -And that's true of older games too (not that I've come across a game from my childhood that I couldn't easily play again one way or another without Linux.)

Linux advocates react so violently to AI because AI breaks the telephony chain that their 'community' culture depends on.

Linux advocacy survives on oral tradition, selective memory, and unverifiable claims.
AI destroys all three.

We have 3 decades of Loonixtard culture relying on vague anecdotes, outdated truths, hearsay from authorities, and unverified claims. Each retelling distorts the original, and the distortion becomes the new truth especially on sites like Reddit where truth is determined by feel good vibes or updoots.

AI can break the cycle by facilitating checking of claims against data, comparing historical sources, and detecting contradictions. The old "just say it confidently and nobody will check" strategy is failing, and it's destroying their walled gardens.

AI is immune to the emotional manipulation tactics used by Loonixtards. Their advocacy extends from just outright lies to relying on shame, guilt, fear, tribalism and moral superiority.

Handwaving is a thing of the past. They can no longer retort "it's your hardware / distro / config / knowledge", or quip "works on my machine" in an age where even the most incompetent / lazy person can highlight, right click and send to CoPilot, DeepSeek, etc.

Linux advocacy is built on quasi‑religious faith and AI is immune to that.

Before AI, Linux advocates could control the narrative because normies didn't know enough to challenge them. I could write an article or two a day for r/linuxsucks101 using the old ways (search engine), while AI allows me to explore my ideas faster and bring more accuracy to my articles.

And it's not just me: Anyone can easily fact check their statements. (Like Windows forcing Lenovo to change the right Ctrl button) and not get whatever the Loonixtards decided to updoot based on vibes.

It's a wrench in the works for a group that relies on controlling the story.

The BSD community is even more against AI, but from what little I've seen; the arguments are different. AI isn't just here all of the sudden: it's improving / evolving. Eventually the arguments will not exist, and they'll have to either adopt to keep up or fall behind. Linux is already decades behind.

...

Most of this article was hand-typed and heavily edited by someone prone to RSI/ tendonitis, and the ideas for it came from that same human.

Haiku is what Linux users claim Linux is!

Linux is a patchwork of 1 kernel, 900 distros, 14 init systems, 6 audio stacks, 5 display servers, 20 packaging formats, and 47 forks of the same terminal emulator.

Haiku is a single OS, vision, desktop, toolkit, package manager, way to configure things.

Haiku gives you actual control because the system is small enough that a single human can understand it. Linux is "control" in the same way a scrapyard is "modular architecture."

Haiku is lightweight because the OS is actually small, not because you removed half the system to make it boot faster.

Haiku is stable because:

• the OS is one cohesive unit
• the UI, drivers, and kernel are designed together
• there's no "mix and match"

Haiku is actually user‑friendly:

• consistent UI
• predictable behavior
• sane defaults
• no “learn 12 subsystems to change your audio device”

Haiku is what Linux users pretend Linux is when talking to normal people.

Linux is not great for desktops, and the community knows it, which is why they keep inventing new DEs every 18 months.

Haiku is a desktop OS built as a desktop OS.
-It's the only FOSS OS that actually behaves like one.

You won't get "your fault: wrong distro", or tribes fighting each other with Haiku.

Haiku is the fantasy Linux users sell, without the fragmentation, the duct tape, or the "works on my machine" toxicity.

And anyone that's been around here knows how important the licensing is, so...

License	Compensation Mechanism	Flexibility	Transparency	Dual Licensing
Haiku License	Enforces fair compensation via defined clauses	Moderately flexible	Very high, with open docs	Supports commercial dual licensing
Apache 2.0 License	Relies on community goodwill (no built-in mechanism)	Highly flexible	High	Not explicitly supported
MIT License	No integrated compensation; purely permissive	Extremely flexible	Very high	Possible through external arrangements
GNU GPL v3	Indirect compensation via copyleft obligations	Less flexible	Very high	Typically does not support dual licensing

- hxxps://dev.to/bobcars/unveiling-haiku-license-a-comprehensive-exploration-and-review-1d0l

(domain apparently b@nned here)

Bombal is a symptom: A walking case study in how "networking educator" YouTube mutated into a content‑farm ouroboros that eats its own credibility while smiling at the camera.

Bombal's channel runs on a predictable three‑phase cycle:

1. "I'm just asking questions" He brings on a guest with a spicy claim (AI doom, cybersecurity apocalypse, Linux miracle, Windows betrayal). He nods politely while the guest says something unhinged.
2. "This changes EVERYTHING" The thumbnail: shocked face, red arrows, neon text. The video: a 40‑minute interview where Bombal speaks for 90 seconds total.
3. "Here's the course link" The outro: "If you want to learn more, check out my course." The course: the same CCNA fundamentals he's been repackaging since the Obama administration.

Bombal's interviews also fall into three categories:

1. The Expert Who Actually Knows Things These are rare. When they appear, Bombal becomes a polite NPC who says "That’s amazing" every 4 minutes.
2. The Evangelist With a Product to Sell Bombal nods. The guest shills. The audience gets a 20‑minute infomercial disguised as "industry insight."
3. The Guy Who Should Not Be Given a Microphone Bombal's brand is now "platforming people who say things like 'AI will replace 90% of jobs by next Tuesday.'"

He never challenges or pushes back. -Just smiles like a man that knows the CPM is good.

Bombal's Linux content is the funniest part because:

1. He treats Linux like a foreign exchange student he's trying to impress.
2. Every Linux video is titled like he's discovered fire.
3. He interviews people who say "Linux is the future" while using Windows to screen‑share.

He's perpetually amazed by things the Linux community stopped being impressed by in 2009.