preview


posts tagged #linuxsucks


I recently came across the Stop Omarchy website, and it pretty much sums up why I find the Linux community so fucking exhausting, and also part of why I gave up on linux entirely.
This campaign explicitly tells maintainers:
“For open-source maintainers, don’t accept bug reports that arise on Omarchy systems.”
Not “require a reproducible example.” Reject them as part of a political boycott. There are also lists of companies to boycott and people to avoid for funding the project.
Apparently, appreciating someone’s software means endorsing their entire worldview. For these people, everything is political. Someone with the wrong opinions takes a piss? That’s a fascist piss, and now the toilet manufacturer needs to issue an apology.
Demanding that everyone else participate in your moral outrage, right down to rejecting users’ bug reports only tells us making better software clearly isn’t the priority. You only care about policing ideological purity.
Anyway, this is one more of the many reasons I think desktop Linux will NEVER become mainstream. These insufferable people are likely the same people dismissing your problems on linux, saying “skill issue” and “pebcak”. The same people telling you that you’re failing as a person if you are running Windows or macOS. All they do is get in the way of progress and irritate everyone. And they’ve almost completely infested the linux space.
TL;DR: The year of the Linux desktop can wait. I have some moral grandstanding to do.
Edit: to everyone saying “then stay on Windows”: look at the name of this community and breathe a sigh of relief. Omarchy is still a Linux distro, with the same fragmentation and usability problems that put us off desktop Linux in the first place. Mocking the level of outrage around it doesn’t mean any of us is about to install the thing, or even look in its general direction.
I recently came across the Stop Omarchy website, and it pretty much sums up why I find the Linux community so fucking exhausting, and also part of why I gave up on linux entirely.
This campaign explicitly tells maintainers:
“For open-source maintainers, don’t accept bug reports that arise on Omarchy systems.”
Not “require a reproducible example.” Reject them as part of a political boycott. There are also lists of companies to boycott and people to avoid for funding the project.
Apparently, appreciating someone’s software means endorsing their entire worldview. For these people, everything is political. Someone with the wrong opinions takes a piss? That’s a fascist piss, and now the toilet manufacturer needs to issue an apology.
Demanding that everyone else participate in your moral outrage, right down to rejecting users’ bug reports only tells us making better software clearly isn’t the priority. You only care about policing ideological purity.
Anyway, this is one more of the many reasons I think desktop Linux will NEVER become mainstream. These insufferable people are likely the same people dismissing your problems on linux, saying “skill issue” and “pebcak”. The same people telling you that you’re failing as a person if you are running Windows or macOS. All they do is get in the way of progress and irritate everyone. And they’ve almost completely infested the linux space.
TL;DR: The year of the Linux desktop can wait. I have some moral grandstanding to do.
Edit: to everyone saying “then stay on Windows”: look at the name of this community and breathe a sigh of relief. Omarchy is still a Linux distro, with the same fragmentation and usability problems that put us off desktop Linux in the first place. Mocking the level of outrage around it doesn’t mean any of us is about to install the thing, or even look in its general direction.
BSD is a single, integrated operating system.
FreeBSD ships kernel + userland + core utilities as one unified project. Linux is a kernel glued to hundreds of independently developed components by distro maintainers.
For production servers, consistency beats “infinite customization.” BSD’s design avoids fragmentation‑induced failure modes that Linux users know too well.
Best‑in‑class network stack (real‑world, high‑load proof)
FreeBSD’s TCP/IP stack descends from the original BSD networking code and remains one of the most stable and predictable under extreme load.
Under heavy load, FreeBSD degrades gracefully instead of collapsing. Linux can be faster in bursts, but BSD is more predictable at scale.
FreeBSD’s configuration layout is stable and predictable.
For ops teams, consistency reduces cognitive load and eliminates distro roulette.
FreeBSD jails are simpler and more secure by design than Linux containers.
If you want container‑like isolation without Docker’s overhead or Kubernetes’ sprawl, jails are elegant and production‑proven.
Real‑world testimony from high‑traffic companies:
Linux can be faster in some benchmarks, but BSD is often more stable in production.
Cleaner long‑term maintenance
FreeBSD’s integrated design means:
FreeBSD wins decisively in:
BSD is a single, integrated operating system.
FreeBSD ships kernel + userland + core utilities as one unified project. Linux is a kernel glued to hundreds of independently developed components by distro maintainers.
For production servers, consistency beats “infinite customization.” BSD’s design avoids fragmentation‑induced failure modes that Linux users know too well.
Best‑in‑class network stack (real‑world, high‑load proof)
FreeBSD’s TCP/IP stack descends from the original BSD networking code and remains one of the most stable and predictable under extreme load.
Under heavy load, FreeBSD degrades gracefully instead of collapsing. Linux can be faster in bursts, but BSD is more predictable at scale.
FreeBSD’s configuration layout is stable and predictable.
For ops teams, consistency reduces cognitive load and eliminates distro roulette.
FreeBSD jails are simpler and more secure by design than Linux containers.
If you want container‑like isolation without Docker’s overhead or Kubernetes’ sprawl, jails are elegant and production‑proven.
Real‑world testimony from high‑traffic companies:
Linux can be faster in some benchmarks, but BSD is often more stable in production.
Cleaner long‑term maintenance
FreeBSD’s integrated design means:
FreeBSD wins decisively in:
It’s bad enough that LiGNUts tend to be anti-work scrubs that cost taxpayers’ money, but they also cost gamers for their flippant returns.
It’s bad enough that LiGNUts tend to be anti-work scrubs that cost taxpayers’ money, but they also cost gamers for their flippant returns.
Linux despite receiving subsidies and government grants requires extra engineering, support, and QA work that OEMs must pay for themselves. Windows is cheaper for OEMs than Linux. Windows is proprietary and Linux is “free,” but the OEM math flips upside‑down.
Microsoft does give OEMs massive volume discounts.
It’s not a conspiracy. OEMs get these deals because:
OEMs including Linux must pay for:
They further cannot take advantage of cheaper board components like different bluetooth, sound, or WiFi, that are often swapped out for better cost in Windows PCs/ mainboards. (Why ‘works on my machine’ with the same mainboard is just ignorant assholiness and their anecdotes aren’t welcome.)
When you’re paying for commie Linux through taxes as well as paying certification costs; you’re literally paying 2 hidden fees.
Linux despite receiving subsidies and government grants requires extra engineering, support, and QA work that OEMs must pay for themselves. Windows is cheaper for OEMs than Linux. Windows is proprietary and Linux is “free,” but the OEM math flips upside‑down.
Microsoft does give OEMs massive volume discounts.
It’s not a conspiracy. OEMs get these deals because:
OEMs including Linux must pay for:
They further cannot take advantage of cheaper board components like different bluetooth, sound, or WiFi, that are often swapped out for better cost in Windows PCs/ mainboards. (Why ‘works on my machine’ with the same mainboard is just ignorant assholiness and their anecdotes aren’t welcome.)
When you’re paying for commie Linux through taxes as well as paying certification costs; you’re literally paying 2 hidden fees.
A Single Maintainer, Countless Packages, and Sudden Silence
Artem Polishchuk (“atim”), a Fedora maintainer responsible for numerous packages including Wayfire and labwc according to community reports, stopped responding roughly six months ago, and every package under his stewardship has ceased receiving updates.
-It’s simply the reality of volunteer labor
Other distros relying on the work will feel the effect.
The only distributions somewhat insulated from maintainer disappearance are those backed by paid corporate maintenance: RHEL (not Fedora), Ubuntu, and SUSE.
A Single Maintainer, Countless Packages, and Sudden Silence
Artem Polishchuk (“atim”), a Fedora maintainer responsible for numerous packages including Wayfire and labwc according to community reports, stopped responding roughly six months ago, and every package under his stewardship has ceased receiving updates.
-It’s simply the reality of volunteer labor
Other distros relying on the work will feel the effect.
The only distributions somewhat insulated from maintainer disappearance are those backed by paid corporate maintenance: RHEL (not Fedora), Ubuntu, and SUSE.
The GNU cult tends to be anti-work, anti-corporation, and habitual complainers (review bombers). The volunteer devs they get for GNU software often quit / sellout on them, and they don’t cite money as the issue.
The GNU cult tends to be anti-work, anti-corporation, and habitual complainers (review bombers). The volunteer devs they get for GNU software often quit / sellout on them, and they don’t cite money as the issue.
Linux users love to blame Windows for “over-writing” the boot loader. Linux doesn’t have a special feud with Windows. -Linux has a feud with any OS that expects sane bootloader behavior.
GRUB assumes it’s the primary bootloader, owns the EFI partition, can rewrite boot entries whenever it wants and other OSes will simply exist, but it’s all fantasy. Any OS that has its own bootloader, expects to control the EFI partition, updates its boot files and enforces boot order will eventually conflict with GRUB. -GRUB and LiGNUt advice are the problem! Windows is just the most common / most noticed by people.
Linux dual‑booting breaks with any OS that has a real bootloader. Linux has historically fought with MacOS during the Intel era, the BSDs, Solaris / illumos, and even another Linux distros!
UEFI was supposed to fix dual‑booting, but made it worse. -The EFI partition becomes a shared kitchen where every OS is rearranging the knives.
Windows gets blamed simply because it’s popular. When GRUB breaks BSD, the 0.0001% of people dual‑booting BSD just shrug and reinstall.
The only stable method: separate drives, separate bootloaders. -And it’s much less wait to choose the OS through BIOS/UEFI that way. -Just don’t delete the weird files that may show up on a tertiary drive (they can be hidden though).
Linux users love to blame Windows for “over-writing” the boot loader. Linux doesn’t have a special feud with Windows. -Linux has a feud with any OS that expects sane bootloader behavior.
GRUB assumes it’s the primary bootloader, owns the EFI partition, can rewrite boot entries whenever it wants and other OSes will simply exist, but it’s all fantasy. Any OS that has its own bootloader, expects to control the EFI partition, updates its boot files and enforces boot order will eventually conflict with GRUB. -GRUB and LiGNUt advice are the problem! Windows is just the most common / most noticed by people.
Linux dual‑booting breaks with any OS that has a real bootloader. Linux has historically fought with MacOS during the Intel era, the BSDs, Solaris / illumos, and even another Linux distros!
UEFI was supposed to fix dual‑booting, but made it worse. -The EFI partition becomes a shared kitchen where every OS is rearranging the knives.
Windows gets blamed simply because it’s popular. When GRUB breaks BSD, the 0.0001% of people dual‑booting BSD just shrug and reinstall.
The only stable method: separate drives, separate bootloaders. -And it’s much less wait to choose the OS through BIOS/UEFI that way. -Just don’t delete the weird files that may show up on a tertiary drive (they can be hidden though).



-If Linux advertising was honest.



-If Linux advertising was honest.

Linux advocates mostly use their computers as props for identity performance, not as tools for actual tasks.
Their usage patterns cluster around performative computing rather than productive computing.
This is the single most consistent behavioral trait.
They spend huge amounts of time:
It’s not about accomplishing tasks — it’s about being seen as someone who knows how.
This is why they love:
It’s cosplay, not computing.
They reinstall their OS more often than they use it.
Patterns:
This is not normal computer usage — it’s hobbyist identity maintenance.
If you track their actual time spent:
Linux advocacy is their main computing workload.
They use their machines to:
Their computer is a megaphone, not a tool.
This is the “Sisyphus loop” of Linux usage.
They spend enormous time:
The machine becomes a puzzle box — not a workstation.
A surprising amount of their computer time is:
It’s meta‑usage: using the computer to consume content about the computer.
They love:
But rarely use the machine for real workloads like:
Benchmarks become a substitute for actual productivity.
This is the least technical but most important.
Linux advocates use their machines to:
The computer becomes a symbol of righteousness.
Not a tool.
They strategically avoid:
Their usage patterns are shaped by avoidance, not capability.
If you map their behavior, Linux advocates mostly use their computers for:
Actual productive computing is the minority use case.
-unedited response from CoPilot

Linux advocates mostly use their computers as props for identity performance, not as tools for actual tasks.
Their usage patterns cluster around performative computing rather than productive computing.
This is the single most consistent behavioral trait.
They spend huge amounts of time:
It’s not about accomplishing tasks — it’s about being seen as someone who knows how.
This is why they love:
It’s cosplay, not computing.
They reinstall their OS more often than they use it.
Patterns:
This is not normal computer usage — it’s hobbyist identity maintenance.
If you track their actual time spent:
Linux advocacy is their main computing workload.
They use their machines to:
Their computer is a megaphone, not a tool.
This is the “Sisyphus loop” of Linux usage.
They spend enormous time:
The machine becomes a puzzle box — not a workstation.
A surprising amount of their computer time is:
It’s meta‑usage: using the computer to consume content about the computer.
They love:
But rarely use the machine for real workloads like:
Benchmarks become a substitute for actual productivity.
This is the least technical but most important.
Linux advocates use their machines to:
The computer becomes a symbol of righteousness.
Not a tool.
They strategically avoid:
Their usage patterns are shaped by avoidance, not capability.
If you map their behavior, Linux advocates mostly use their computers for:
Actual productive computing is the minority use case.
-unedited response from CoPilot
WSL is better than Linux in several ways, and those ways are exactly the kinds of things that matter to home users who just want their machine to work!
On bare‑metal Linux:
On WSL:
WSL never has to deal with:
WSL inherits Windows’ hardware support, which is objectively the best in the world.
Bare‑metal Linux has:
WSL has:
You don’t get the “update roulette” Linux users deal with (and fear).
GPU acceleration is easier and more stable on WSL. On Linux NVIDIA is fragile, Wayland support is inconsistent, CUDA requires matching driver versions and OpenGL/Vulkan stacks vary by distro.
WSL avoids:
Bare‑metal Linux lets you:
If you break your WSL distro, you delete it and reinstall it.
Your computer still boots. Your files are still safe.
WSL distros are just:
WSL is perfect for development environments because it’s isolated, disposable, and reproducible.
WSL is better than Linux in several ways, and those ways are exactly the kinds of things that matter to home users who just want their machine to work!
On bare‑metal Linux:
On WSL:
WSL never has to deal with:
WSL inherits Windows’ hardware support, which is objectively the best in the world.
Bare‑metal Linux has:
WSL has:
You don’t get the “update roulette” Linux users deal with (and fear).
GPU acceleration is easier and more stable on WSL. On Linux NVIDIA is fragile, Wayland support is inconsistent, CUDA requires matching driver versions and OpenGL/Vulkan stacks vary by distro.
WSL avoids:
Bare‑metal Linux lets you:
If you break your WSL distro, you delete it and reinstall it.
Your computer still boots. Your files are still safe.
WSL distros are just:
WSL is perfect for development environments because it’s isolated, disposable, and reproducible.
Linux kills SSDs faster, because parts of the Linux ecosystem (including systemd) generate unnecessary write‑amplification, and Linux is slower than Windows/BSD to adopt modern SSD‑preservation techniques.
Linux is fragmented, slow to standardize, and full of subsystems that thrash storage because nobody agrees on sane defaults.
Systemd isn’t horrible, but it’s extremely heavy on disk writing and Lennart Pottering is no longer involved with it. On a busy system, it produces continuous low‑level write thrashing, especially for laptops with flaky suspend/resume, desktops with misbehaving services, servers with noisy logs, and distros that crank journald verbosity up.
BSD, OpenRC, Runit, and s6 barely touch the disk unless something actually happens. Systemd touches it because something might happen.
Windows adopted SSD‑aware defaults early with automatic TRIM, write-coalescing, aggressive caching (why it sometimes appears to use more RAM), NTFS metadata batching, and predictable journaling.
Linux DEs generate pointless writes, like GNOME tracker indexing, KDE Baloo indexing, Flatpak metadata churn, Snap loop-mount spam, electron apps spamming logs, browser cache directories with no write-limits, and package managers re-writing entire meta-data trees.
Windows and macOS throttle background writes. -Linux does not.
Linux swap behavior is notoriously aggressive. Systemd‑oomd monitors memory pressure and writes state constantly. Cgroups v2 memory accounting causes extra metadata writes. Swappiness defaults are often too high. Zram is not enabled by default on most distros. Browsers + Electron apps push Linux into swap more easily due to fragmentation
When Linux hits swap, SSDs get hammered.
Linux kills SSDs faster, because parts of the Linux ecosystem (including systemd) generate unnecessary write‑amplification, and Linux is slower than Windows/BSD to adopt modern SSD‑preservation techniques.
Linux is fragmented, slow to standardize, and full of subsystems that thrash storage because nobody agrees on sane defaults.
Systemd isn’t horrible, but it’s extremely heavy on disk writing and Lennart Pottering is no longer involved with it. On a busy system, it produces continuous low‑level write thrashing, especially for laptops with flaky suspend/resume, desktops with misbehaving services, servers with noisy logs, and distros that crank journald verbosity up.
BSD, OpenRC, Runit, and s6 barely touch the disk unless something actually happens. Systemd touches it because something might happen.
Windows adopted SSD‑aware defaults early with automatic TRIM, write-coalescing, aggressive caching (why it sometimes appears to use more RAM), NTFS metadata batching, and predictable journaling.
Linux DEs generate pointless writes, like GNOME tracker indexing, KDE Baloo indexing, Flatpak metadata churn, Snap loop-mount spam, electron apps spamming logs, browser cache directories with no write-limits, and package managers re-writing entire meta-data trees.
Windows and macOS throttle background writes. -Linux does not.
Linux swap behavior is notoriously aggressive. Systemd‑oomd monitors memory pressure and writes state constantly. Cgroups v2 memory accounting causes extra metadata writes. Swappiness defaults are often too high. Zram is not enabled by default on most distros. Browsers + Electron apps push Linux into swap more easily due to fragmentation
When Linux hits swap, SSDs get hammered.
BSD didn’t just ship TCP/IP it shipped the reference implementation that everyone copied.
Linux inherited networking culture from BSD.
BSD’s security lineage is absurdly influential:
Linux distros ship OpenSSH and pf-derived concepts because BSD did the hard work.
BSD’s storage innovations are quietly everywhere:
BSD storage philosophy: correctness first, performance second, hype never.
A shocking amount of “standard Unix” tooling is actually BSD-origin:
If you’ve ever typed ifconfig, ps, kill, or netstat, you’ve touched BSD DNA.
BSD introduced architectural ideas that shaped modern OS design:
Linux containers are conceptually BSD jails with marketing.
BSD’s influence on the actual backbone of the internet is massive:
If it moved packets in the 80s, 90s, or early 2000s, it probably ran BSD code.
macOS, iOS, iPadOS, watchOS, tvOS — all built on:
Every iPhone is a BSD descendant.
Consumer Electronics
BSD-origin tools that became universal:
BSD contributed ideas that shaped how engineers think:
Linux culture often prioritizes velocity; BSD prioritizes durability.
BSD didn’t just give the world TCP/IP — it gave the world the shape of modern computing: sockets, filesystems, logging, containers, security tooling, DNS, routing, storage frameworks, and the OS foundations inside every iPhone and PlayStation.
BSD didn’t just ship TCP/IP it shipped the reference implementation that everyone copied.
Linux inherited networking culture from BSD.
BSD’s security lineage is absurdly influential:
Linux distros ship OpenSSH and pf-derived concepts because BSD did the hard work.
BSD’s storage innovations are quietly everywhere:
BSD storage philosophy: correctness first, performance second, hype never.
A shocking amount of “standard Unix” tooling is actually BSD-origin:
If you’ve ever typed ifconfig, ps, kill, or netstat, you’ve touched BSD DNA.
BSD introduced architectural ideas that shaped modern OS design:
Linux containers are conceptually BSD jails with marketing.
BSD’s influence on the actual backbone of the internet is massive:
If it moved packets in the 80s, 90s, or early 2000s, it probably ran BSD code.
macOS, iOS, iPadOS, watchOS, tvOS — all built on:
Every iPhone is a BSD descendant.
Consumer Electronics
BSD-origin tools that became universal:
BSD contributed ideas that shaped how engineers think:
Linux culture often prioritizes velocity; BSD prioritizes durability.
BSD didn’t just give the world TCP/IP — it gave the world the shape of modern computing: sockets, filesystems, logging, containers, security tooling, DNS, routing, storage frameworks, and the OS foundations inside every iPhone and PlayStation.
Torvalds is confronting a reality where AI‑augmented code discovery, bug surfacing, and exploit generation are now part of the ecosystem he maintains. He’s adapting because the kernel can’t pretend these tools don’t exist anymore.
For 3 decades, kernel development has been shaped by human‑found bugs, written patches, and human‑paced review cycles. Modern LLM‑based static analysis and fuzzing pipelines can surface hundreds of potential issues in minutes, generate PoCs for exploit chains, mutate inputs faster than syzkaller ever could, and find “weird machine” states humans wouldn’t think to test.
-Torvalds can no longer ignore that.
Ignoring AI became impossible once it started surfacing kernel‑relevant bugs. For years, Torvalds dismissed AI codegen as “garbage”, “dangerous”, and “not helpful”. -Then AI tools started finding UB patterns, surfacing concurrency hazards, generating syzkaller-style crash reproducers, identifying memory-safety regressions, and flagging suspious pointer lifetimes… he could no longer treat it as noise.
-Linus was late to the party.
The kernel community was moving on without him. Maintainers were discussing AI‑generated patch floods, new tooling to triage AI‑found issues, stricter patch acceptance rules, more emphasis on reproducible test cases, more skepticism toward AI‑assisted contributions, and more automation around review queues.
-He adapts when the ecosystem forces adaptation. -He’s not a visionary
Torvalds is confronting a reality where AI‑augmented code discovery, bug surfacing, and exploit generation are now part of the ecosystem he maintains. He’s adapting because the kernel can’t pretend these tools don’t exist anymore.
For 3 decades, kernel development has been shaped by human‑found bugs, written patches, and human‑paced review cycles. Modern LLM‑based static analysis and fuzzing pipelines can surface hundreds of potential issues in minutes, generate PoCs for exploit chains, mutate inputs faster than syzkaller ever could, and find “weird machine” states humans wouldn’t think to test.
-Torvalds can no longer ignore that.
Ignoring AI became impossible once it started surfacing kernel‑relevant bugs. For years, Torvalds dismissed AI codegen as “garbage”, “dangerous”, and “not helpful”. -Then AI tools started finding UB patterns, surfacing concurrency hazards, generating syzkaller-style crash reproducers, identifying memory-safety regressions, and flagging suspious pointer lifetimes… he could no longer treat it as noise.
-Linus was late to the party.
The kernel community was moving on without him. Maintainers were discussing AI‑generated patch floods, new tooling to triage AI‑found issues, stricter patch acceptance rules, more emphasis on reproducible test cases, more skepticism toward AI‑assisted contributions, and more automation around review queues.
-He adapts when the ecosystem forces adaptation. -He’s not a visionary
Asahi didn’t “fail”. Asahi delivered exactly what a small, highly technical project could realistically deliver. What failed was the Linux community’s fantasy projection. The Linux hype machine rewards potential, not outcomes.
When a project promises things like “full hardware support”, “a new architecture”, yadda yadda, it becomes the buzz on Reddit, Lemmy, and Hacker News immediately.
Reverse‑engineering culture creates unrealistic expectations. Linux users love the idea that “If we just reverse‑engineer it hard enough, we can beat the vendor.” But reverse‑engineering is slow, fragile, and dependent on a tiny number of experts. Asahi had maybe 3–5 people doing the heavy lifting while the hype acted like it had 300.
The community treats every project like a Windows/macOS replacement. Even when the project itself says:
“This is experimental, incomplete, and not meant for daily use.”
The GNU community of course hears:
“This will dethrone Apple.”
It will happen repeatedly, predictably, and as long as Linux is a thing because the Linux ecosystem keeps generating the same conditions before reality arrives: 2-5 years of slow driver work, partial hardware support, niche usability, tiny contributor base, dev burnout, and ‘it works’ (but not better than the vendor OS).
Linux has 3 decades of failing to live up to hype, and the situation is mirrored for:
Asahi didn’t fail, Linux hype failed (as it always does.)
It’s not like typical Linux users can afford a Mac, and those that could probably wouldn’t gimp it with Linux. -2% of 2%
Asahi didn’t “fail”. Asahi delivered exactly what a small, highly technical project could realistically deliver. What failed was the Linux community’s fantasy projection. The Linux hype machine rewards potential, not outcomes.
When a project promises things like “full hardware support”, “a new architecture”, yadda yadda, it becomes the buzz on Reddit, Lemmy, and Hacker News immediately.
Reverse‑engineering culture creates unrealistic expectations. Linux users love the idea that “If we just reverse‑engineer it hard enough, we can beat the vendor.” But reverse‑engineering is slow, fragile, and dependent on a tiny number of experts. Asahi had maybe 3–5 people doing the heavy lifting while the hype acted like it had 300.
The community treats every project like a Windows/macOS replacement. Even when the project itself says:
“This is experimental, incomplete, and not meant for daily use.”
The GNU community of course hears:
“This will dethrone Apple.”
It will happen repeatedly, predictably, and as long as Linux is a thing because the Linux ecosystem keeps generating the same conditions before reality arrives: 2-5 years of slow driver work, partial hardware support, niche usability, tiny contributor base, dev burnout, and ‘it works’ (but not better than the vendor OS).
Linux has 3 decades of failing to live up to hype, and the situation is mirrored for:
Asahi didn’t fail, Linux hype failed (as it always does.)
It’s not like typical Linux users can afford a Mac, and those that could probably wouldn’t gimp it with Linux. -2% of 2%
(They aren’t worth catering to) -Even if they had stable ABI/API in the kernel (they don’t.) The smarter question: why not BSD?
(They aren’t worth catering to) -Even if they had stable ABI/API in the kernel (they don’t.) The smarter question: why not BSD?
And it is NOT the ‘entire’ Internet.
And it is NOT the ‘entire’ Internet.
TLDR: Valve/Steam has never issued a general warning to users about the frame‑pacing/timing‑logic issues in certain games that make them effectively unplayable or unbeatable on SteamOS despite “running.”
-Not in patch notes, Proton release notes, Deck Verified criteria, store‑page warnings, and not in any public communication.
They do not test for timing bugs, broken physics, or unstable frametime behavior. Valve has never warned users about games that “run” but have broken timing logic under Proton/SteamOS. Major issues arise when there’s physics tied to uncapped framerate, games that rely on Windows-specific timing APIs, games that behave differently at 40/60/90 Hz and games where frame pacing instability causes input desync or impossible difficulty spikes.
Valve does not mark these games as “Unsupported,” even though the gameplay is functionally broken.
If the game launches and renders frames, Valve considers it “working.” Even if the frametime graph looks like a seismograph, the game’s logic runs too fast or too slow, boss fights become impossible, rhythm/timing games desync, cutscenes skip or break scripting, or a time trial becomes unbeatable mid-game.
No warnings. No labels. No store‑page notices.
Valve won’t even tell you, "this game runs poorly on SteamOS, is broken under Proton, or “works better on Windows”. If you want to find problems, you need to look at the fixes, but there are no ‘heads ups’.
TLDR: Valve/Steam has never issued a general warning to users about the frame‑pacing/timing‑logic issues in certain games that make them effectively unplayable or unbeatable on SteamOS despite “running.”
-Not in patch notes, Proton release notes, Deck Verified criteria, store‑page warnings, and not in any public communication.
They do not test for timing bugs, broken physics, or unstable frametime behavior. Valve has never warned users about games that “run” but have broken timing logic under Proton/SteamOS. Major issues arise when there’s physics tied to uncapped framerate, games that rely on Windows-specific timing APIs, games that behave differently at 40/60/90 Hz and games where frame pacing instability causes input desync or impossible difficulty spikes.
Valve does not mark these games as “Unsupported,” even though the gameplay is functionally broken.
If the game launches and renders frames, Valve considers it “working.” Even if the frametime graph looks like a seismograph, the game’s logic runs too fast or too slow, boss fights become impossible, rhythm/timing games desync, cutscenes skip or break scripting, or a time trial becomes unbeatable mid-game.
No warnings. No labels. No store‑page notices.
Valve won’t even tell you, "this game runs poorly on SteamOS, is broken under Proton, or “works better on Windows”. If you want to find problems, you need to look at the fixes, but there are no ‘heads ups’.
Linux doesn’t have a native Layer‑7 application firewall API
Windows and macOS have OS‑level frameworks that:
Any Linux “application firewall” tries to work with mechanisms that were never designed for it.
Why Linux app firewalls break (OpenSnitch, Portmaster, etc.)
Linux apps spawn dozens or hundreds of short‑lived helper processes.
A firewall trying to track each one is fighting the OS. Windows/macOS utilize app identity or code‑signed bundles.
Games and anti‑cheat/DRM hate syscall interception. -These systems detect “unexpected interference” and bail. Outbound firewalling is also bypassable on Linux. It can inject itself into other allowed processes easier than it can on Windows.
Linux has a different security model, which handles the situation differently. It has AppArmor (per-process syscall restrictions), SELinux, fapolicyd/IMA, Firejail, and Flatpack permissions (toggles).
Linux doesn’t have a native Layer‑7 application firewall API
Windows and macOS have OS‑level frameworks that:
Any Linux “application firewall” tries to work with mechanisms that were never designed for it.
Why Linux app firewalls break (OpenSnitch, Portmaster, etc.)
Linux apps spawn dozens or hundreds of short‑lived helper processes.
A firewall trying to track each one is fighting the OS. Windows/macOS utilize app identity or code‑signed bundles.
Games and anti‑cheat/DRM hate syscall interception. -These systems detect “unexpected interference” and bail. Outbound firewalling is also bypassable on Linux. It can inject itself into other allowed processes easier than it can on Windows.
Linux has a different security model, which handles the situation differently. It has AppArmor (per-process syscall restrictions), SELinux, fapolicyd/IMA, Firejail, and Flatpack permissions (toggles).
BSD has better security, load handling, network stack, documentation, cohesion, power efficiency, etc. -Try to explain why BSD isn’t dominant on servers without mentioning the GNU/GPL cult.
Wasting 30-45% power isn’t just about about laptops wasting power anymore, it’s about datacenter‑scale inefficiency caused by architectural gaps in Linux’s power management stack.
CPU idle state handling is worse than Windows Server Linux often fails to enter the deepest C‑states under load patterns that Windows handles correctly.
This is especially bad on:
Linux scheduler inefficiency The Completely Fair Scheduler (CFS) is great for fairness, terrible for power.
This alone can cause 15–25% power waste under mixed workloads.
PCIe ASPM is frequently disabled On servers, Linux often ships with:
Why?
Because vendors disable these features in firmware when Linux drivers don’t reliably support them.
That’s 5–10% wasted power across NICs, NVMe, HBAs, GPUs, accelerators.
Driver power gating is incomplete
Windows drivers are vendor‑authored.
Linux drivers are:
This affects:
Power gating gaps can add 10–20% inefficiency.
Kernel regressions are common and persistent A single kernel update can break:
These regressions often sit unfixed for months, especially in LTS kernels.
BSD has better security, load handling, network stack, documentation, cohesion, power efficiency, etc. -Try to explain why BSD isn’t dominant on servers without mentioning the GNU/GPL cult.
Wasting 30-45% power isn’t just about about laptops wasting power anymore, it’s about datacenter‑scale inefficiency caused by architectural gaps in Linux’s power management stack.
CPU idle state handling is worse than Windows Server Linux often fails to enter the deepest C‑states under load patterns that Windows handles correctly.
This is especially bad on:
Linux scheduler inefficiency The Completely Fair Scheduler (CFS) is great for fairness, terrible for power.
This alone can cause 15–25% power waste under mixed workloads.
PCIe ASPM is frequently disabled On servers, Linux often ships with:
Why?
Because vendors disable these features in firmware when Linux drivers don’t reliably support them.
That’s 5–10% wasted power across NICs, NVMe, HBAs, GPUs, accelerators.
Driver power gating is incomplete
Windows drivers are vendor‑authored.
Linux drivers are:
This affects:
Power gating gaps can add 10–20% inefficiency.
Kernel regressions are common and persistent A single kernel update can break:
These regressions often sit unfixed for months, especially in LTS kernels.
The most rigorous measurement of support comes from analysis (2009–2021). In 2021, U.S. federal agencies invested ~$407 million in OSS development. Code.gov -This is OSS broadly, not Linux-specific.
A 2026 UN/UNESCO/Software Heritage report shows:
-Demonstrating widespread global investment.
Linux-specific cost cannot be isolated because it’s developed by corporations (Red Hat, Intel, Google, Meta, AMD), volunteers, universities (subsidized), and Nonprofits like Linux Foundation.
Government contributions aren’t tracked by project, and are often indirect (unaccounted for), such as with funding research labs that contribute patches.)
The U.S. federal government spends over $100 billion/year on IT contracts. About $12 billion/year is software licensing & development (includes proprietary).
The most rigorous measurement of support comes from analysis (2009–2021). In 2021, U.S. federal agencies invested ~$407 million in OSS development. Code.gov -This is OSS broadly, not Linux-specific.
A 2026 UN/UNESCO/Software Heritage report shows:
-Demonstrating widespread global investment.
Linux-specific cost cannot be isolated because it’s developed by corporations (Red Hat, Intel, Google, Meta, AMD), volunteers, universities (subsidized), and Nonprofits like Linux Foundation.
Government contributions aren’t tracked by project, and are often indirect (unaccounted for), such as with funding research labs that contribute patches.)
The U.S. federal government spends over $100 billion/year on IT contracts. About $12 billion/year is software licensing & development (includes proprietary).
With Linux; you need to keep your whole system updated (which many don’t do because it often causes breakage on Linux.) Windows doesn’t even need a system update (and reboot) to update Windows Defender. Linux users bragging about uptime is really them displaying their ignorance concerning security.

-“We just distrohop or blame ourselves when something bad happens!”
With Linux; you need to keep your whole system updated (which many don’t do because it often causes breakage on Linux.) Windows doesn’t even need a system update (and reboot) to update Windows Defender. Linux users bragging about uptime is really them displaying their ignorance concerning security.

-“We just distrohop or blame ourselves when something bad happens!”
Smartphones have banking, government ID, payment, messaging, and travel apps. Linux has none of these natively.
Phones have hardware-backed keystores, verified boot, mandatory sandboxing, mandatory app permissions, and automatic security patching.
Smartphones get first‑party vendor support, unified SDKs, guaranteed updates, and predictable APIs.
Desktop Linux breaks more often because it’s not a controlled platform. Phones are appliances while Linux desktops are DIY kits.
Smartphones have updates tested against one hardware stack, drivers are unified, firmware is integrated, and apps are vetted.
With Linux, kernel updates can break drivers, DE updates can break extensions, Wayland/X11 fragmentation causes regressions, GPU stack varies by vendor, and Firmware flashing is riskier.
Smartphones have better power management
Phones have aggressive battery optimization (imagine money being incentive), hardware‑software co‑design, and unified sleep states. Thermal management is tuned per device.
Smartphones have better multimedia pipelines with hardware‑accelerated codecs, camera pipelines tuned per sensor, DRM is fully supported, and the audio stack unified.
Smartphones have banking, government ID, payment, messaging, and travel apps. Linux has none of these natively.
Phones have hardware-backed keystores, verified boot, mandatory sandboxing, mandatory app permissions, and automatic security patching.
Smartphones get first‑party vendor support, unified SDKs, guaranteed updates, and predictable APIs.
Desktop Linux breaks more often because it’s not a controlled platform. Phones are appliances while Linux desktops are DIY kits.
Smartphones have updates tested against one hardware stack, drivers are unified, firmware is integrated, and apps are vetted.
With Linux, kernel updates can break drivers, DE updates can break extensions, Wayland/X11 fragmentation causes regressions, GPU stack varies by vendor, and Firmware flashing is riskier.
Smartphones have better power management
Phones have aggressive battery optimization (imagine money being incentive), hardware‑software co‑design, and unified sleep states. Thermal management is tuned per device.
Smartphones have better multimedia pipelines with hardware‑accelerated codecs, camera pipelines tuned per sensor, DRM is fully supported, and the audio stack unified.
What Linux did with NTFS (a janky, reverse‑engineered driver for a proprietary filesystem) is unique to Linux.
FreeBSD, OpenBSD, and NetBSD all support some Linux filesystems, but only the safe, well‑documented, and non‑proprietary ones.
They don’t support:
BSD developers won’t repeat Linux’s NTFS mistake of supporting a filesystem without full specs or stable kernel APIs. They only adopt filesystems that are fully documented, stable and not tied to Linux kernel churn.
MacOS supports:
Apple will not ship write support for:
Apple refuses to take on the liability of writing to foreign filesystems. They don’t want to be blamed for corruption caused by undocumented formats, kernel instability, or third‑party metadata semantics.
Windows is even more conservative than macOS.
Windows supports:
Linux is the only OS that aggressively supports foreign filesystems.
Linux culture encourages experimentation, reverse engineering, volunteer supplied garbage drivers, and distros exposing experimental features. This is why Linux ended up with janky NTFS, HFS, UFS drivers, etc.
NTFS on Linux was a disaster that took 20 years to sort out, and no other OS would subject its users to anything like it.
What Linux did with NTFS (a janky, reverse‑engineered driver for a proprietary filesystem) is unique to Linux.
FreeBSD, OpenBSD, and NetBSD all support some Linux filesystems, but only the safe, well‑documented, and non‑proprietary ones.
They don’t support:
BSD developers won’t repeat Linux’s NTFS mistake of supporting a filesystem without full specs or stable kernel APIs. They only adopt filesystems that are fully documented, stable and not tied to Linux kernel churn.
MacOS supports:
Apple will not ship write support for:
Apple refuses to take on the liability of writing to foreign filesystems. They don’t want to be blamed for corruption caused by undocumented formats, kernel instability, or third‑party metadata semantics.
Windows is even more conservative than macOS.
Windows supports:
Linux is the only OS that aggressively supports foreign filesystems.
Linux culture encourages experimentation, reverse engineering, volunteer supplied garbage drivers, and distros exposing experimental features. This is why Linux ended up with janky NTFS, HFS, UFS drivers, etc.
NTFS on Linux was a disaster that took 20 years to sort out, and no other OS would subject its users to anything like it.
When Ubuntu breaks something, Mint breaks. When Debian freezes for 2 years, Mint freezes. When Ubuntu ships outdated packages, Mint ships outdated packages.
Cinnamon is:
Mint intentionally avoids major updates to avoid breaking things.
Great (j/k) for grandma’s laptop. Not great for gaming, new hardware, or anything performance‑sensitive.
Mint hates Snaps (this actually makes sense for Desktop). Mint barely tolerates Flatpaks. Mint’s repos are old. So, users end up in dependency hell or installing random .debs (binaries, or what Windows users used to be mocked for) from the internet.
“we don’t like the App Store, but we also don’t have our own."
-Mint fans pretend these never happened.
When Ubuntu breaks something, Mint breaks. When Debian freezes for 2 years, Mint freezes. When Ubuntu ships outdated packages, Mint ships outdated packages.
Cinnamon is:
Mint intentionally avoids major updates to avoid breaking things.
Great (j/k) for grandma’s laptop. Not great for gaming, new hardware, or anything performance‑sensitive.
Mint hates Snaps (this actually makes sense for Desktop). Mint barely tolerates Flatpaks. Mint’s repos are old. So, users end up in dependency hell or installing random .debs (binaries, or what Windows users used to be mocked for) from the internet.
“we don’t like the App Store, but we also don’t have our own."
-Mint fans pretend these never happened.
Linux avoids heavy hardware‑error mediation layers because they add complexity and overhead.
Sacrifice:
Linux chooses correctness over uptime.
Sacrifice:
Linux drivers are lean and often run in kernel space.
Sacrifice:
Linux avoids the overhead of virtualization‑based kernel protection.
Sacrifice:
Linux can retire bad RAM pages, but distros rarely enable it because it adds overhead and complexity.
Sacrifice:
Windows compensates for bad RAM; Linux expects good RAM.
Linux desktops are modular and lightweight.
Sacrifice:
Linux avoids heavyweight watchdog frameworks.
Sacrifice:
Linux’s design roots are in server environments.
Sacrifice:
Linux is ‘often’ lighter because it does less to protect you from bad hardware.
Linux avoids heavy hardware‑error mediation layers because they add complexity and overhead.
Sacrifice:
Linux chooses correctness over uptime.
Sacrifice:
Linux drivers are lean and often run in kernel space.
Sacrifice:
Linux avoids the overhead of virtualization‑based kernel protection.
Sacrifice:
Linux can retire bad RAM pages, but distros rarely enable it because it adds overhead and complexity.
Sacrifice:
Windows compensates for bad RAM; Linux expects good RAM.
Linux desktops are modular and lightweight.
Sacrifice:
Linux avoids heavyweight watchdog frameworks.
Sacrifice:
Linux’s design roots are in server environments.
Sacrifice:
Linux is ‘often’ lighter because it does less to protect you from bad hardware.