5 ms·

hint: it has something to do with the fact that Windows machines have a reputation for BSoDing regularly, whereas Linux systems have no such reputation.

lightedman 9y ago
"whereas Linux systems have no such reputation." Hah. I've been through kernel panic hell more times than years in my age, and I'm OLD. You must be real new to the Linux world if you think it has a spotless record. In fact, it's still possible to hardlock the kernel all these years after I reported how. Lemme show you how poorly the Kernel handles an encrypted RAMDisk with a couple configured parameters.
- bkor 9y ago
  > Hah. I've been through kernel panic hell more times than years in my age, and I'm OLD. So why do you pretend NOT to know at all that the kernel handles/provides drivers? If you're so experienced you should be well aware of that.
  - comex 9y ago
    Well, Windows notably switched to a new graphics driver model in Vista that puts parts of graphics drivers in userland, in order to allow them to crash without taking down the system. But I think that's comparable to what Linux has always been doing with Mesa vs. DRM; not sure what the details look like though.
  - lightedman 9y ago
    "So why do you pretend NOT to know at all that the kernel handles/provides drivers?" You're failing at reading and understanding any of my words, which means you're likely looking to start a problem. Okay, I'll play along. I know that the Kernel handles and provides drivers - what you're failing to understand is that I think it's HORRIBLE (and I can prove it hundreds of different ways on any Linux distro excepting maybe SELinux and its flavors.) Wake me up when the entire Linux graphics subsystem can crash without taking the entire computer, or one single app, along with it. Windows can do this. Linux can not. Linux is therefore doing things poorly. Even BSD handles this better. Every other OS excepting Linux has bothered to come into the modern age of graphics subsystems around 2007/2008. Linux is still behind and will remain so for the foreseeable future.
ahartmetz 9y ago
For Linux it's IME not BSODs, but deficiencies in desktop usage situations. A CPU and I/O scheduler that causes sound stuttering (now better than five years ago), or my favorite... CDs with read errors can hang much of the user interface forever and effectively require a restart. Not even mechanically force-ejecting the CD helps. It is AFAIK not due to programming errors in the UI - processes become unkillably stuck. Fortunately it isn't very relevant anymore. It may even have been fixed and I haven't noticed.
- Karunamon 9y ago
  Network drives going away will still reliably hang explorer processes. It’s 2017, there’s no reason to be doing network access on the UI thread anymore.
sunstone 9y ago
I've been using Ubuntu desktop for over ten years. My experience is that every now and then it just stops and needs a hard reset. Not as polite as a BSOD.
orbifold 9y ago
If anything Linux Desktops are way less stable than Windows Desktop. Try crashing a graphics driver on Linux and see what happens and compare that to Windows (it restarts without interrupting operation). Most of the Linux schedulers are awful for interactive use as well. I'm forced to use Debian and Scientific Linux installations at work, they are so much worse at basically anything I've experienced both on Windows and macOS it is not even funny.
- gima 9y ago
  I experience somewhat frequent GPU crashes when playing Diablo3 under Wine with the integrated i3-4150 GPU, but the graphics stack recovers by itself in about a minute. I can then continue from where I left off, sans the application that crashed with it.
  - orbifold 9y ago
    Under Windows the recovery is instant, there is an audible bell and a popup window in the taskbar saying something along the lines of: "The graphics driver has crashed and has been restarted". In any case by now I'm pretty sick of Linux fanboys making fun of people using other operating systems. Using Linux as a Desktop OS, especially if your are not given a chance to modify the installation is an exercise in self-flagellation.

lightedman 9y ago

"whereas Linux systems have no such reputation." Hah. I've been through kernel panic hell more times than years in my age, and I'm OLD. You must be real new to the Linux world if you think it has a spotless record. In fact, it's still possible to hardlock the kernel all these years after I reported how. Lemme show you how poorly the Kernel handles an encrypted RAMDisk with a couple configured parameters.

bkor 9y ago
> Hah. I've been through kernel panic hell more times than years in my age, and I'm OLD. So why do you pretend NOT to know at all that the kernel handles/provides drivers? If you're so experienced you should be well aware of that.
- comex 9y ago
  Well, Windows notably switched to a new graphics driver model in Vista that puts parts of graphics drivers in userland, in order to allow them to crash without taking down the system. But I think that's comparable to what Linux has always been doing with Mesa vs. DRM; not sure what the details look like though.
- lightedman 9y ago
  "So why do you pretend NOT to know at all that the kernel handles/provides drivers?" You're failing at reading and understanding any of my words, which means you're likely looking to start a problem. Okay, I'll play along. I know that the Kernel handles and provides drivers - what you're failing to understand is that I think it's HORRIBLE (and I can prove it hundreds of different ways on any Linux distro excepting maybe SELinux and its flavors.) Wake me up when the entire Linux graphics subsystem can crash without taking the entire computer, or one single app, along with it. Windows can do this. Linux can not. Linux is therefore doing things poorly. Even BSD handles this better. Every other OS excepting Linux has bothered to come into the modern age of graphics subsystems around 2007/2008. Linux is still behind and will remain so for the foreseeable future.

ahartmetz 9y ago

For Linux it's IME not BSODs, but deficiencies in desktop usage situations. A CPU and I/O scheduler that causes sound stuttering (now better than five years ago), or my favorite... CDs with read errors can hang much of the user interface forever and effectively require a restart. Not even mechanically force-ejecting the CD helps. It is AFAIK not due to programming errors in the UI - processes become unkillably stuck. Fortunately it isn't very relevant anymore. It may even have been fixed and I haven't noticed.

Karunamon 9y ago
Network drives going away will still reliably hang explorer processes. It’s 2017, there’s no reason to be doing network access on the UI thread anymore.

sunstone 9y ago

I've been using Ubuntu desktop for over ten years. My experience is that every now and then it just stops and needs a hard reset. Not as polite as a BSOD.

orbifold 9y ago

If anything Linux Desktops are way less stable than Windows Desktop. Try crashing a graphics driver on Linux and see what happens and compare that to Windows (it restarts without interrupting operation). Most of the Linux schedulers are awful for interactive use as well. I'm forced to use Debian and Scientific Linux installations at work, they are so much worse at basically anything I've experienced both on Windows and macOS it is not even funny.

gima 9y ago
I experience somewhat frequent GPU crashes when playing Diablo3 under Wine with the integrated i3-4150 GPU, but the graphics stack recovers by itself in about a minute. I can then continue from where I left off, sans the application that crashed with it.
- orbifold 9y ago
  Under Windows the recovery is instant, there is an audible bell and a popup window in the taskbar saying something along the lines of: "The graphics driver has crashed and has been restarted". In any case by now I'm pretty sick of Linux fanboys making fun of people using other operating systems. Using Linux as a Desktop OS, especially if your are not given a chance to modify the installation is an exercise in self-flagellation.