Most people were conditioned by more “user-friendly” systems to ignore the content of error messages because only an expert can make sense of “Error: 0x8000000F Unknown Error”. So they don’t even try, and that’s how they put themselves in a Yes, doas I say! situation.
It’s not even obscure, context dependent errors. I’ve had many professional system administrators not understand what “connection was closed by peer” meant.
In the admins defense. “Closed by peer” can indicate everything from a safe closure to an unsafe closure to a server connection terminating which causes the peer to terminate.
Like that’s a fair point of confusion.
What bugs me is when the error says something stupid specific and obvious such as JavaScript heap out of memory or dd:error writing *pathname*: No space left on device
But most error messages are in plain English first (plus some numbers and codes).
No, they see white (gray actually) blocky text on a black background, they think the machine is broken and go into panic mode. Instead of reading.
Which is kinda what you said.
And because people don’t read error messages, many applications/sites/etc don’t even put them, or if they do they either don’t have any public facing documentation to actually figure out what that code means, or they do and it might as well be nothing
that’s why any manual worth their salt has a “quick start” section at the beginning (I say this knowing most man pages fail at this or put it at the end which is super unhelpful)
Just give me common uses and flags, you can have your more indepth stuff at the end
Most people don’t even read the error messages. They’re never gonna read a whole manual.
Most people were conditioned by more “user-friendly” systems to ignore the content of error messages because only an expert can make sense of “Error: 0x8000000F Unknown Error”. So they don’t even try, and that’s how they put themselves in a
Yes, do as I say!situation.It’s not even obscure, context dependent errors. I’ve had many professional system administrators not understand what “connection was closed by peer” meant.
Well, to be fair, I’m also not very well versed in the intricacies of connecting with British nobility.
Have you tried turning the rape island off and on again?
One day I’ll catch that jerk Peer! So rude, always closing my connections!
In the admins defense. “Closed by peer” can indicate everything from a safe closure to an unsafe closure to a server connection terminating which causes the peer to terminate.
Like that’s a fair point of confusion.
What bugs me is when the error says something stupid specific and obvious such as
JavaScript heap out of memoryordd: error writing *pathname*: No space left on deviceYeah, but they literally couldn’t tell me if it’s a problem with the network or something else. It’s like it’s in a totally different language
yea thats fully understandable. also no idea why this post just showed in my feed, didn’t mean to revive a 4 month old comment 😅
That’s the beauty of the fediverse :)
But most error messages are in plain English first (plus some numbers and codes).
No, they see white (gray actually) blocky text on a black background, they think the machine is broken and go into panic mode. Instead of reading.
Which is kinda what you said.
What about the fucking manual?
Kama Sutra?
I guess you get good at Unix and refrigerator by reading it, so why not?
Don’t fuck the manual!
And because people don’t read error messages, many applications/sites/etc don’t even put them, or if they do they either don’t have any public facing documentation to actually figure out what that code means, or they do and it might as well be nothing
that’s why any manual worth their salt has a “quick start” section at the beginning (I say this knowing most man pages fail at this or put it at the end which is super unhelpful)
Just give me common uses and flags, you can have your more indepth stuff at the end