CLI really?
OK. I’ve become the grumpy old man telling you kids to turn down that noise! My friends would tell you I really like all kinds of that loud noise so it seems slightly strange. I keep reading comments and tweets, seeing presentations, and online tutorials how the command line is the best thing since sliced bread (sliced bread apparently was a big deal in the early 1900s). I repeatedly see and hear how I‘m not a “real” man, “real” programmer, “real” nerd, and even how potential employers may frown upon the using of a GUI-based tool, viewing it as some sort of crutch or cheat. When I heard it once it didn’t register, twice I chuckled, three, four, five … oh my! I think they’re serious not just being ironic.
If they (you know who “they” are) gave out medals for the CLI Olympics those of us who started our careers in the 70s have earned multiple gold medals, or perhaps platinum or unobtainium. We certainly didn’t do it as a show of compchismo we did it because it was all we had … blowing snow, bare feet, uphill both ways … you know the story! I shouldn’t be surprised though because even bell-bottoms and silk shirts came back in fashion and if that’s possible why not command-based computing? If it rolls back far enough I’m looking forward to toggling in patches through the control panel of a DG Eclipse, that was when a control panel was a CONTROL panel — all 16 bits of it!
Alright! I understand the utility of the command line, I really do. If I knew, having worked for workstation manufacturers, how many times I’ve typed ls, cd, awk, ps, grep et al. I might need a padded room. I’m really talking about the “right of passage” use of command line interfaces in deference to their graphical counterparts. There may be couple of forces at play.
If the command line offers more power or is easier to use then by all means have at it. Let’s be honest, if this is true it’s a failure of the graphical application implementation. Seemingly we have a potential chicken and egg (I win $5 for using egg in a technical blog) situation. Because of the popularity of CLI usage, applications are “dumbed down” for the “not a real” class user or may not have the necessary resources dedicated to them. Perhaps shortcomings in the applications are the driver for “real” class user adoption of the CLI.
I have to take a moment to reflect back on the growth of GUI environments, Lisa OS/Mac OS (I fondly remember the Byte magazine with the Lisa on the cover), X Windows and Microsoft Windows, and how elated we were to potentially leave the command line behind. As a side note I got pretty excited when we upgraded our VAX 11/785 environment to amber VT220 terminals from the old VT100s … to be fair the programming environment and keyboard were vastly improved. Being able to navigate a directory tree with a mouse and drag and drop a file from one directory to another … it was magical, strike that, it was flippin’ heaven. Guess what? I didn’t feel any less a “real” programmer even though I knew how to use cd/mv or DIRECTORY/COPY (VMS style).
Please stop denigrating those who choose not to use the CLI when they are given a viable graphical alternative. Graphical application developers step up the game if you're being out functioned by CLI. Employers you are making a mistake if you mark down a candidate because they use GitHub through their IDE or some other such nonsense. Truth be told to the “real” class user, learning the commands for Git (as with most other CLIs) is “really” not that impressive, generally it’s a memory and typing challenge. Using vi in place of a graphical IDE, while it warms my heart for the same reason as csh, is a very personal choice.
Chill! To each their own. It’s “real” cool, at least to me, that you can create formal language and use yacc to generate a parser! It is! It doesn’t make you any better or worse than the next gal. Frankly, if command line is so cool why use an emoji when you could go old school }:-> However, for those of you who still think the B and A in bash stand for bad a$$ remember there are those of us who were writing sh before it was Bourne Again and before some of you were born.
You kids there … Get off my lawn!
Reminds me of the stones.. you can't be a man cause you don't right the same commands as me... lol
I'm coming from the "other side", not big into programming unless I have to (born & bread without built in logic, but I make killer illustrations!) If computer graphics were ALL command-line, then I would have been out of business a long time ago. Thank God for GUIs. I've been teaching graphics, web design, and multimedia for a while now, and one of the classes I teach is a foundation in Drupal CMS. It has taken me quite a while to learn it on my own (because of some backwards approaches in tutorials) and then, turn around to teach it efficiently to students to master the basics and come out on the other side with a full-blown site. I love the way Drupal handles content. But, I would love to customize the look of the site, especially since I teach my students HTML & CSS, even they could do it. It has proven very difficult to do so. Every tutorial or training I encounter on theme building means more complicated code or worse, Drush (the command line for Drupal). Why on earth would I want to use a command line or have such complicated code to deal with in this endeavor when a CMS is supposed to be all about ease of use, not coding. Don't get me wrong, I could do it, given a great learning curve, and I do love those dedicated programmers under the hood. I don't have that kind of time. And, don't get me started on hand-coding and programming animation. I'm much better with a brush than I am with programming. Just give me my Adobe Animate (formerly Flash) and convert the code for me. The circles I draw with a GUI tool are much prettier and a take shorter amount of time than if I were to sit there and hand code a circle and try to make it move! Long live GUIs! Get off my lawn Drush!