To a slightly lesser extent, that’s also true of Windows - severe malfunctions are less likely to happen, but when they do happen, fixing them is almost always an absolute clusterfuck, and when it isn’t, it’s downright impossible.
At least Linux usually has some useful error messages. On Windows, you get a fucking “Error Code 0x0000000f” and looking it up usually leads to some confidently incompetent layperson telling the OP to make sure their drivers are updated, or someone who managed to trick Microsoft into giving them a title of “assistant” on the official forum suggesting Windows Diagnostics like that’s ever done anything useful, and at that point I just wanted to fucking die.
I’ll take a fucked-up xorg.conf over that clown show.
To a slightly lesser extent, that’s also true of Windows - severe malfunctions are less likely to happen, but when they do happen, fixing them is almost always an absolute clusterfuck, and when it isn’t, it’s downright impossible.
At least Linux usually has some useful error messages. On Windows, you get a fucking “Error Code
0x0000000f” and looking it up usually leads to some confidently incompetent layperson telling the OP to make sure their drivers are updated, or someone who managed to trick Microsoft into giving them a title of “assistant” on the official forum suggesting Windows Diagnostics like that’s ever done anything useful, and at that point I just wanted to fucking die.I’ll take a fucked-up xorg.conf over that clown show.
To be fair a lot of the time a blue screen is shitty drivers…
Blue screens are usually a defense against shitty code fucking over the hardware.
It halts the entire computer to prevent the hardware from being damaged.
I don’t know what Linux does to prevent that, but I hope it has something similar.
The Linux equivalent is a kernel panic