4 ms·
I really dislike these cutesy google-style error messages à la "oops something went wrong" and "Aw, snap ..." - Often, their information value is zero: they don
by sdfx 18y ago
I really dislike these cutesy google-style error messages à la "oops something went wrong" and "Aw, snap ..." - Often, their information value is zero: they don't explain to you how to solve the problem or what went wrong (maybe with the exception of the frozen error message). When you are frustrated because something isn't working these messages can get on your nerves fast.
It's great if you can package the information in a funny way, but if you can't I'd take function over form any time.
- wyday 18y agoIf they could "explain to you how to solve the problem or what went wrong" then they wouldn't need to show a vague error message. They'd just fix the problem.
- verdant 18y agoTypically, though, if the browser could display some kind of information on the nature of the error, this could give a savvy user something they could type into a search engine or ask an intelligent question about on a forum, which might help them fix whatever is causing their problem. This might not apply as much to the web, where the problem is likely a malfunctioning network connection, or a problem with the web server (or server side code). But it could help where the user is having a problem trying to accomplish something with an application which they will never be able to do until they change something on their end, or attempt it a different way.
- verdant 18y agoI agree, and to be fair to Jeff, he does point this out. It kind of gets lost in the main idea of his post. FTA: "Don't get me wrong. Your error messages should always be informative and helpful. That's not optional."