Although I haven’t encountered it yet, having not yet installed the preview version of Windows 8, apparently, the BSOD remains, in a friendly incarnation.
I remember back in mid-2009, we had a similarly tongue-in-cheek Error 500 page for Connect. It had a cat. It had “internets”. It was awesome.
Apparently, not everyone thought so, and someone complained to Paul (@ppedrazzi) about it. Unprofessional or something.
Rich (@rmanalan) and I shook our heads on this one given the nature of Connect as social app, not a mission-critical one, but we changed it to be more serious.
Error messaging is an under-served bit of UX/UI. Taking it too lightly can grate on your users, as at least one Tumblr user noted during their epic downtime in January:
The Oatmeal recently suggested a new Tumblr downtime mascot for instance, and it looks like Tumblr has adopted it as of the other day – a quick reaction – but should they really be spending their time doing this, as opposed to fixing the real issue? Are their priorities right?
There’s a big difference between a BSOD and a 404 or 500 on a web app.
I wonder if this will make it into the released version of Win 8.
Anyway, do flip or funny error messages bother you? Does it depend on how valuable the failing service or application is?
Find the comments.
Update: Upon further review, this is an informational improvement over the old BSOD. They’ve toned down the language, omitting scary words like “damage” and dumping nearly all the technical information, which only serves to confuse or scare the average user. I like it, even without the emoticon.