You Don't Need a GUI
Full disclosures:<p>1) I have an App - <a href="https:&#x2F;&#x2F;nocommandline.com" rel="nofollow">https:&#x2F;&#x2F;nocommandline.com</a> - that is the opposite of this i.e. it says you should use a GUI instead of CLI (for a specific set of scenarios).<p>2) I&#x27;m not a 9-5 programmer even though I have a computing background<p>At a very high level - I generally disagree with &#x27;you don&#x27;t need a GUI&#x27; or &#x27;CLI is better than a GUI&#x27;<p>At a nuanced level, I would say - it all depends. Sometimes CLI is much better than a GUI, other times it is the opposite. It all depends on what you are doing and who is doing what.<p>Software is all about automation and making life easier for you and&#x2F;or others. If instead of having to remember a bunch of commands that I have to type, I can just click and get the same result, then click for me is better. It has made my life easier&#x2F;simpler which is the essence of automation. GUI also becomes more useful for commands that you don&#x27;t get to execute regularly. And GUI makes it easier for others to uptake the technology&#x2F;learn it. Think about it - programmers tend to use IDEs to write their code and not notepad because IDE colors the text and so they know which are variables, restricted values, etc.<p>There is the argument that you can&#x27;t automate GUIs. That is true in some contexts but in others, GUIs are usually built on top of the raw CLI commands so you have both worlds.<p>In other situations (and generally speaking), CLI is much more powerful because you have complete control of the &#x27;innards&#x27; of the program. For such, I would say - yea, CLI all the way.