You do realize that Linux is intended to be run on ECC memory, while Windows has been built with many features to compensate and is therefore more resilient for almost all home users. Your anecdotes are funny because they lack all technical merit (typical Linux propaganda).
Even Linus Torvalds would shake his head at the nonsense LiGNUts put out there.
Just fyi, you are talking to a nutter. That person created the linuxsucks community and seems to spend all waking (probably sleeping too) hours thinking about linux and how to get mad at linux. Don Quixote has nothing on this guy
Data integrity is a hardware problem, not an OS problem.
The myth that Linux is stable enough that you don’t need ECC unless you’re running ZFS or a database is wrong. A flipped bit corrupts memory before the OS sees it.
-ECC protects the OS. The OS cannot protect itself.
Windows has the most aggressive consumer‑grade fault‑tolerance stack with WHEA, bad‑page retirement, PCIe AER recovery, GPU/driver subsystem restart, VBS integrity enforcement, core offlining, and memory poisoning.
-These features dramatically reduce crashes on unreliable hardware.
ECC is the only one to detect single‑bit errors, correct single‑bit errors, detect multi‑bit errors, and prevent silent corruption from propagating. It’s not ‘Linux stability’ - it’s literally ECC (which most consumer desktops and laptops don’t have)!
-Servers need ECC because server workloads demand correctness (and Linux doesn’t even try to deliver that because they don’t have to).
Cosmic rays, electrical noise, and manufacturing defects literally hit hardware, not software. -That famous blue screen in front of an audience during a Windows presentation? -Nothing to be ashamed about (but they could’ve used ECC)!
If the hardware lies, the OS has no way to know. Even Windows Server requires ECC. Enterprise Linux distros recommend ECC. It’s about physics: not the OS.
Removed by mod
You do realize that Linux is intended to be run on ECC memory, while Windows has been built with many features to compensate and is therefore more resilient for almost all home users. Your anecdotes are funny because they lack all technical merit (typical Linux propaganda).
Even Linus Torvalds would shake his head at the nonsense LiGNUts put out there.
Removed by mod
Just fyi, you are talking to a nutter. That person created the linuxsucks community and seems to spend all waking (probably sleeping too) hours thinking about linux and how to get mad at linux. Don Quixote has nothing on this guy
Removed by mod
Data integrity is a hardware problem, not an OS problem.
The myth that Linux is stable enough that you don’t need ECC unless you’re running ZFS or a database is wrong. A flipped bit corrupts memory before the OS sees it.
-ECC protects the OS. The OS cannot protect itself.
Windows has the most aggressive consumer‑grade fault‑tolerance stack with WHEA, bad‑page retirement, PCIe AER recovery, GPU/driver subsystem restart, VBS integrity enforcement, core offlining, and memory poisoning.
-These features dramatically reduce crashes on unreliable hardware.
ECC is the only one to detect single‑bit errors, correct single‑bit errors, detect multi‑bit errors, and prevent silent corruption from propagating. It’s not ‘Linux stability’ - it’s literally ECC (which most consumer desktops and laptops don’t have)!
-Servers need ECC because server workloads demand correctness (and Linux doesn’t even try to deliver that because they don’t have to).
Cosmic rays, electrical noise, and manufacturing defects literally hit hardware, not software. -That famous blue screen in front of an audience during a Windows presentation? -Nothing to be ashamed about (but they could’ve used ECC)!
If the hardware lies, the OS has no way to know. Even Windows Server requires ECC. Enterprise Linux distros recommend ECC. It’s about physics: not the OS.
Random thought - do you use AI to author your comments/posts?
Removed by mod
I admire your composure, knowledge and patience.
Removed by mod