Terminal Dreams, Part II
As of the time of this writing, it's been about a day since my adventure in attempting to use the terminal for all tasks began. This will be somewhat abbreviated compared to the last post, for the purpose of getting it online in a reasonable time.
The first thing to note is that the experiment wasn't an unqualified success, but it could have been if I had been more persistent (or prepared). I ran into a problem that initially seemed to require the use of a web application, and since support for these is largely nonexistent from the command line, I'm sorry to note that I resorted to my mobile device to get past the issue (as I recall, it was my password manager). As it turned out, that lapse could have been avoided, but I didn't have the patience to work it out when I was attempting to get past whatever authentication request I had run into.
One day isn't sufficient time to get acclimated to this environment (even though I had some experience already). I spent a lot of my day yesterday trying to either remember or learn the various steps necessary to do something I would have taken for granted before. This initial learning curve and setup process is a serious impediment towards using a CLI environment on a regular basis. The time you save by being focused on your work can be offset by the time it takes to get something running in the first place, and it is easier to change how you use a GUI than it is to learn about all of the 'gotchas' that might hinder your CLI usage.
The main problems I ran into that I couldn't directly resolve in the time frame:
It's been an interesting and reasonably productive and educational experience. As you may have surmised by now, I intend to avoid a second consecutive day of terminal use, but I wouldn't rule out doing this sort of thing again in the future, even if it is for somewhat shorter stretches.
Stay tuned for another article, exploring some of my thoughts on the differences between the CLI and GUI paradigms.