Why Linux tech-support articles use terminal commands instead of the GUI

Oct 03, 2012 16:03

I do it myself. I wrote some get-started-with-Linux articles for the Register a while ago and got panned for that in the comments.

There are good reasons, though. It's just that all the n00bs and Windows lusers are scared of text, they want point-and-drool. ;-)

The things are these:

* with text, you can copy & paste - you can't do that with  ( Read more... )

repurposed, tech support, mailing list post, writing

Leave a comment

Comments 14

vexen October 3 2012, 14:08:09 UTC
But let it also be known that some of us Windows addicts appreciate the high utility of CLIs.

Reply

liam_on_linux October 3 2012, 14:30:50 UTC
:-)

How do you like PowerShell? Tried 3 yet?

Reply

vexen October 4 2012, 09:31:39 UTC
I don't use/need things like PowerShell; I churn out temporary little programs to do 'stuff' at the drop of a hat. And you seriously don't want to know what my default platform is!

Reply

liam_on_linux October 4 2012, 12:33:55 UTC
DOS batch files? QBASIC?

Reply


baljemmett October 3 2012, 14:10:26 UTC
Whilst I agree with your point, this bit raised an eyebrow:

text is exact & unambiguous. Didn't work? You typed it wrong.

... alternatively somebody along the line didn't proofread properly and something crucial got clobbered. For instance, I've lost count of the number of times I've seen command lines and code excerpts reduced to nonsense because somebody forgot to escape a < when they crafted their HTML.

Reply

liam_on_linux October 3 2012, 14:31:11 UTC
Fair point, well made - but easily fixed in these online days.

Reply

pne October 4 2012, 10:40:43 UTC
Or double hyphens turned in en dashes or em dashes. “command -option=value” is not going to work.

Or, for that matter, ASCII quotes turned into “smart ones”. touch “file name with spaces in it” is going to create six files, not one.

Reply


bryangb October 3 2012, 14:39:43 UTC
"got panned for that in the comments."

As I suspect you well know, Reg (and Inq, and...) articles are all about traffic - so if you're writing comment or flame fodder, you're doing a good job. (-:

Reply

liam_on_linux October 3 2012, 15:17:36 UTC
True, I guess. Lots of comments saying it's all bollocks still means lots of readers!

Reply

bryangb October 3 2012, 15:37:01 UTC
I guess it's best if there's also some "Hear hear" type comments - otherwise every-bloody-thing would be Mac-Windows flamefests.

Reply

liam_on_linux October 4 2012, 12:35:09 UTC
Oh, I get a few of those, too.

& I was much touched by the concern shown by the staffers the first time I got a load as well. "Don't read them," "there's a reason we call them commentards" and so on - very solicitous. :¬D

Reply


(The comment has been removed)

vexen October 4 2012, 09:36:14 UTC
These are very well put comments, vicarage and I'd wish I'd had the clarity to say the same. Although 'cos I'm a natural contrarian... I'm going to make a counter-point to your awesome comment:

"Your problem is your professional job is dealing with people in their private mode."

... if everyone took simple things home with them, like, consider everything case-sensitive then it would improve their lives in general and not just in the IT world. I am sure that CLI activity is good for the general working of the brain. So perhaps, people ought to be taking some of the OPs lessons home with them.

Reply


(The comment has been removed)

lovingboth October 4 2012, 19:04:02 UTC
While I agree with Liam, it would help if *ix were not so keen on the 'you asked for it, you got it' approach to CLI commands which make it so easy to destroy data.

Mind you, it annoys me when several imagemagick commands don't do what you want unless you add the 'Yes, command to shrink an image, I really want you to shrink that image' switch to the command.

Reply


Leave a comment

Up