> How the hell a modern OS can be frozen completely shut by some runaway python script running in a VS code
That isn't a just Linux thing. You can easily fork-bomb (or equivalent) Windows/iOS/other and so forth, especially (though not only) if running as a privileged user.
> And then non-obvious issues that just "appear" out of nowhere
That is definitely not something that I've never seen when using Windows! Where it has happened to me under Linux it has been eventually traced to a hardware issue or a bad update (the latter I've experienced on both those OSs over the years and the former will affect everything).
> > And then non-obvious issues that just "appear" out of nowhere
>That is definitely not something that I've never seen when using Windows!
Case in point: my laptop (running the Windows 10 it came with) recently stopped hibernating properly, well it hibernates OK but half the time when it wakes up the screen does not turn on, and this evening it has decided that it doesn't want to be asleep while plugged in. If I tell it to sleep (through power key or start menu) while plugged in it does very temporarily and then returns to the login screen. If I tell it to sleep when running on battery it does but immediately wakes up once power is connected.
While Linux distros are far from free from random problems at times, in my experience Windows exhibits them more and tends to be harder to diagnose because more is hidden.
> That isn't a just Linux thing. You can easily fork-bomb (or equivalent) Windows/iOS/other and so forth, especially (though not only) if running as a privileged user.
I've crashed DWM with WSL before, by doing something completely unrelated to Windows.
What happens is you start getting the solitaire effect because suddenly no windows have graphics buffers anymore
That isn't a just Linux thing. You can easily fork-bomb (or equivalent) Windows/iOS/other and so forth, especially (though not only) if running as a privileged user.
> And then non-obvious issues that just "appear" out of nowhere
That is definitely not something that I've never seen when using Windows! Where it has happened to me under Linux it has been eventually traced to a hardware issue or a bad update (the latter I've experienced on both those OSs over the years and the former will affect everything).