Which is kinda sad. The console always feels like a more precise way to deal with a problem. So it’s like people are saying “Using a mouse is too scary, I’d rather use a WiiMote while wearing mittens”
Every computer on every operating system, will inevitably face an issue of some kind at some point. Something you need to troubleshoot.
And if 100% of the troubleshooting is to copy/paste commands into terminal? Yeah. It IS necessary to type things into terminal.
This isn’t a case of “Terminal is the easy way, but you can find help tutorials using the GUI.”
This is a case of every tutorial is “copy/paste these commands into your terminal, and if something goes wrong you better know what the errors are even saying”
So when a non techie sees “python error”, their reaction will be “THERE ARE SNAKES INSIDE MY PC??? THEY’RE CAUSING ERRORS!!!”
Some of my favourite ones from trying to learn this new system include:
invalid argument
Uh… I just typed in a magic incantation that takes up two lines on this text thing.
Which.Fucking.One!?
no such file or directory
The final three words above apply here too. I got this one because a file I downloaded that was supposed to do something had …insert long string of technobabble from SO that included the word shahbang, I swear! It took him over ten minutes to find whatever all the treknobabble he uttered meant and then half a second to fix.
So it’s not even fear that’s at issue. It’s blank incomprehension when the error message is about as useful as those dummy lights in '80s-era cars that just said “ENGINE”.
It’s more than that, too. Even when there are GUI things (like the network manager in my system now) the GUIs are badly designed (because it turns out that UX design is an actual, learnable, technical field!), and, further, inconsistent from one piece to another so there’s little in the way of shared learning. When you learn one of these little GUI utilities you’ve learned … that one … GUI … utility.
At that point you might as well be typing stuff like ls -laR ~/Documents | awk '{print $9}' | grep -v '^\.' | xargs -I{} file {} | grep -i 'ascii\|unicode\|utf' | cut -d: -f1 | xargs -I{} sh -c 'head -n 5 "{}" | nl -ba -s": " | sed "s/^/$(basename {}): /"' | less -N
(Fake command line supplied by long-suffering SO who got a kick out of making something incredibly stupid.)
This is self-fulfilling bullshit. Everyone is saying that typing words is somehow scary, so everyone is scared of typing words.
Average user doesn’t really has more problems with console, either they care enough to google how to fix the problem, and do whatever Internet tells them, or they don’t and they ask for help and kick the problem down the chain. Will the solution involve typing words or clicking checkboxes is kind of irrelevant
Yeah, the average user doesn’t want to do scary console shit. Linux won’t replace windows until people don’t need to type console commands.
Which is kinda sad. The console always feels like a more precise way to deal with a problem. So it’s like people are saying “Using a mouse is too scary, I’d rather use a WiiMote while wearing mittens”
People don’t need to type console commands. They’re just the easiest way to tell someone how to do something in text.
Every computer on every operating system, will inevitably face an issue of some kind at some point. Something you need to troubleshoot.
And if 100% of the troubleshooting is to copy/paste commands into terminal? Yeah. It IS necessary to type things into terminal.
This isn’t a case of “Terminal is the easy way, but you can find help tutorials using the GUI.”
This is a case of every tutorial is “copy/paste these commands into your terminal, and if something goes wrong you better know what the errors are even saying”
So when a non techie sees “python error”, their reaction will be “THERE ARE SNAKES INSIDE MY PC??? THEY’RE CAUSING ERRORS!!!”
Some of my favourite ones from trying to learn this new system include:
invalid argumentUh… I just typed in a magic incantation that takes up two lines on this text thing.
Which. Fucking. One!?
no such file or directoryThe final three words above apply here too. I got this one because a file I downloaded that was supposed to do something had …insert long string of technobabble from SO that included the word shahbang, I swear! It took him over ten minutes to find whatever all the treknobabble he uttered meant and then half a second to fix.
So it’s not even fear that’s at issue. It’s blank incomprehension when the error message is about as useful as those dummy lights in '80s-era cars that just said “ENGINE”.
You’re about a decade or two out of date with your knowledge here.
It’s more than that, too. Even when there are GUI things (like the network manager in my system now) the GUIs are badly designed (because it turns out that UX design is an actual, learnable, technical field!), and, further, inconsistent from one piece to another so there’s little in the way of shared learning. When you learn one of these little GUI utilities you’ve learned … that one … GUI … utility.
At that point you might as well be typing stuff like
ls -laR ~/Documents | awk '{print $9}' | grep -v '^\.' | xargs -I{} file {} | grep -i 'ascii\|unicode\|utf' | cut -d: -f1 | xargs -I{} sh -c 'head -n 5 "{}" | nl -ba -s": " | sed "s/^/$(basename {}): /"' | less -N(Fake command line supplied by long-suffering SO who got a kick out of making something incredibly stupid.)
This is self-fulfilling bullshit. Everyone is saying that typing words is somehow scary, so everyone is scared of typing words.
Average user doesn’t really has more problems with console, either they care enough to google how to fix the problem, and do whatever Internet tells them, or they don’t and they ask for help and kick the problem down the chain. Will the solution involve typing words or clicking checkboxes is kind of irrelevant