Very interesting even if I don’t use Windows: I suspect similar stuff is going on in modern Linux desktops but I would not have imagined such a sequence of events.
My laptop (maybe other Ubuntu 20.04 users too?) has an issue where occasionally coming out of Suspend will display the password prompt but not accept any input for a while. It’s rare enough to be an annoyance and not a show stopper, but frequent enough that this blog post immediately made me think of it. I wonder what kinds of tools Linux has to dig into something like this.
That’s a good one! Very windows-y, where you have about three different Convenient Features working at cross-purposes with each other and making life suck. Seems to me like, for how often crash dumps get uploaded to MS, there should just be an email-spool-like queue for it. (This isn’t me being snarky; I wish everything could have the wealth of automatic bug report and analysis data MS must get from this.) On the other hand, I suppose that waiting to upload the entire dump before restarting the program is an effective form of back-pressure… just maybe not the back-pressure one would want.
Very windows-y, where you have about three different Convenient Features working at cross-purposes with each other and making life suck
I hate windows as much as the next linux weenie, but just this week I was debugging exactly this class of issue on linux. After updating a snap, if you started it via synapse (but not if you started it from gnome-terminal) its AppArmor profile would use paths from a previous version & thus would fail.
Once your OS has got three Convenient Features, they’ll work at cross-purposes.
Oh, totally. This certainly isn’t Windows exclusive. I made the mistake of trying out KDE this morning and it took 30 minutes to get my computer usable again. I just always get the feeling from reading Raymond Chen blog posts that 90% of Windows’s problems are its own features stepping on themselves and/or being horribly abused by clueless customers. When that happens with Linux though, you at least get to pretend that nobody has a plan. :-P
Very interesting even if I don’t use Windows: I suspect similar stuff is going on in modern Linux desktops but I would not have imagined such a sequence of events.
My laptop (maybe other Ubuntu 20.04 users too?) has an issue where occasionally coming out of Suspend will display the password prompt but not accept any input for a while. It’s rare enough to be an annoyance and not a show stopper, but frequent enough that this blog post immediately made me think of it. I wonder what kinds of tools Linux has to dig into something like this.
That’s a good one! Very windows-y, where you have about three different Convenient Features working at cross-purposes with each other and making life suck. Seems to me like, for how often crash dumps get uploaded to MS, there should just be an email-spool-like queue for it. (This isn’t me being snarky; I wish everything could have the wealth of automatic bug report and analysis data MS must get from this.) On the other hand, I suppose that waiting to upload the entire dump before restarting the program is an effective form of back-pressure… just maybe not the back-pressure one would want.
I hate windows as much as the next linux weenie, but just this week I was debugging exactly this class of issue on linux. After updating a snap, if you started it via synapse (but not if you started it from gnome-terminal) its AppArmor profile would use paths from a previous version & thus would fail.
Once your OS has got three Convenient Features, they’ll work at cross-purposes.
Oh, totally. This certainly isn’t Windows exclusive. I made the mistake of trying out KDE this morning and it took 30 minutes to get my computer usable again. I just always get the feeling from reading Raymond Chen blog posts that 90% of Windows’s problems are its own features stepping on themselves and/or being horribly abused by clueless customers. When that happens with Linux though, you at least get to pretend that nobody has a plan. :-P