memes

Sure, because Linux never has hardware crashes ...

Windows user here. I don't have a fear of BSODs.

On the other hand, I have "Linux users are elitist jerks" syndrome, which stops me from switching to Linux, due to a fear of Linux users might be elitist jerks. This can be only cured by massive improvements to the Linux community, and a debugger that has an actual GUI for Linux (no, I don't care about whatever cute little script you've written for GDB for a semi-automated testsuite for command line utility that converts one obscure format into another).

Linux Syndrome:

When nobody asked but somehow the solution is Linux.

I used to dual-boot and use my Win10 for gaming.

But in the middle of Vermintide 2 I kept getting BAD BSoDs seemingly at random! None of the typical steps seemed to help. Probably something NVIDIA related I dunno.

I was gonna "refresh this system" and all Windows told me after "We're getting this ready." was: "Can't. Dunno why. Sorry."

But hey, switching over to my OpenSUSE Tumbleweed install made the game play really smooth, and no crashes! And soon, I discovered it ran all my other games just fine or even better as well!

I haven't touched that Win10 install in ages, and will probably drop it in favor of VMing it really soon.

The only real holdout is that my VR headset is WMR. That really sucks. :(

NGL, some distros will give you the anxiety that the next update will brick your OS as well

Sigh… c/linuxmemes continues to leak

Other cures include literally just restarting your PC once a month so it can install updates.

I'm a Linux user, and I have "X11 decides to lock up the entire system irrecoverably for no reason" syndrome. Should probably look into wayland...

This is what got me to switch to Linux (arch btw). I was getting blue/green screens 1-2x a week and it almost always ruined a gaming experience.

Now I can bork my system during an update, but at least I can game smoothly. My system hasn't crashed once while in the middle of something (I have, however, fucked up my system post update and without a Time shift backup ready to go which merited a full reinstall - but it's been a good learning experience overall)

I haven't seen a blue screen in years.

Yes, Linux Preachers, I am a Windows user.

I'd literally rather risk losing everything to a blue screen than use something arcane, deliberately difficult to use, unnecessarily complicated and bereft of any interesting or useful programs.

Linux is great for niche scenarios, like software development, but horrible for most daily use and any critic who pretends otherwise is ignorant or lying.

Linux machines don't crash unexpectedly, because if they do, it's your fault for configuring it wrong and you should have expected it.

I saw that happen once in a big presentation.

There was a team of students presenting their work to ~200 people. Right in the middle, a pop-up says updates are finished and the computer needs to restart. It has a helpful 60-second countdown, but “cancel” is grayed out, so all they can do is watch.

I was only in the audience and I still have nightmares.

Linux will have an equialvent of BSoD soon. https://www.phoronix.com/news/Linux-DRM-Panic-QR-Codes

Since when did the Blue Screen concept change from being an actual error screen to simply the Windows update screen?

I'm guessing shortly after Windows began implementing aforementioned update screen?

This is the first I've heard it referred to as the Blue Screen.

For reference: https://wikipedia.org/wiki/Blue_screen_of_death

99 percent of the time I've had to deal with a bsod in Windows, it was a bad driver (Intel controllerless Wi-Fi, for one) or a software issue (Malwarebytes Premium or Kaspersky + insert networking app here). Sometimes it's a hardware problem (stupid ASUS laptops with builtin RAM), and rarely, a bad disk clone (gotta do that bcdboot)