[smoyer]

I agree that knowing the CLI (of whatever OS you use) is a good idea but ...

I'm not going to take the challenge as I have the opposite problem. Since I wrote software for 20 years before I had a GUI, I find myself using the CLI too much in certain cases. I've been trying to learn more of the hot-keys for the windowed tools that I do use ... and how to do some of my CLI tasks in a windowed environment.

One curious note: I could live with 8.3 file names (since I did for years) but I ditched Mac OSX because I couldn't tolerate it being case-insensitive.

[thedufer]

I'm curious why the case-insensitivity bothered you. Do you often write files that differ only in case? Since all of the shells' tab completion remains case-sensitive, many CLI-centric programmers don't even notice that OS X is case-insensitive.

[winash]

Maybe you should take the "One month GUI challenge" :), I wrote this for folks who are just getting started I believe that once knlowing the CLI gives you some confidence about uour computer and sets you up for easier learning in the future.

[smoyer]

A "one month GUI challenge" would be interesting ... I'm not sure I could do it though. Would we exclude interactions with remote servers? If I use a GUI editor to create Ansible playbooks that are run against a server farm, that feels a bit like cheating.

The example in your article was great (sort) - what other tools can't you live without on the CLI? Here are a few of my favorites:

- unique - sed - grep - wc

[winash]

I usually get a lot of this, can you find me number of x from this file and y that DB table for December .

I find myself using 'join' a lot.