Conversation
Notices
-
Embed this notice
@chris I pick on Windows here because it's about the only one that for decades has been only giving error codes (and as numbers rather than words like SIGSEGV, so not rememberable and not web-search able) instead of error messages.
And I think error codes are only acceptable for hardware-level errors and heavily constrained embedded software.
- feld likes this.
-
Embed this notice
@lanodan Yeah I've been on Unix for most of the last
25 years. Longer if you count dialup shell accounts. Used Windows 95 back
in the day some, and DOS some. In the last decade or so, I started noticing
just how terrible error messages were on smartphone apps and webapps. I
hadn't realized Windows started the trend.
-
Embed this notice
@chris I'm from unixes, where you get logs or at worst some canned message like "Block device required".
Webapps come from a lot of windows mindset where error messages aren't seen as important.
-
Embed this notice
@lanodan
That is an absolutely terrible error message. Go go OpenSSL!
In fairness to it, I might be able to decipher it with effort.
It's a little better than "Error: success", maybe, and a vast improvement
over the sort of error messages a lot of apps and webapps give. "There
was an error. Try again later." Those kind are all too common and just
inculcate learned helplessness.
-
Embed this notice
"Error reading data from TLS socket: error:00000001:lib(0)::reason(1)"
I love error handling.