[jacquesm]

True. But the point was that X doesn't do it in my experience, maybe I'm unique, maybe not you'll need more numbers. But the ONE windows box we have here has the same problem. So I could make the exact opposite case ("windows crashes, X does not, windows should learn from 'X'") and it would still just be anecdotal evidence.

The author suggests that windows has 'the solution' for these kinds of crashes, that is why saying but windows does it too is relevant, it somewhat negates his assertion.

If windows would really be rock solid I think I would have a different experience, and - sadly - I'm not alone in that.

What the underlying reasons are is anybodies guess, but by bitching about it it is not going to get solved.

His parting shot is:

"I'm sure the blame-game will be played thoroughly in the comments, but it will only detract from the real problem here. The Linux desktop needs a modern, robust, and advanced graphics stack, which makes sure that crashes and bugs remain isolated, without them affecting the users' work. Microsoft has shown us how it's done, now all the X world needs to do is follow."

Whereas if he would simply contact the maintainers of the code with a reproducible error and a stacktrace I'm sure they'd be happy to help.