Faster, generally easier, cheaper (in terms of start-up time).<p>I have no problem with choosing between GUI or CLI interfaces, but I find myself doing far more work via the CLI than with GUI.<p>My desktop is comprised of several (usually 6) virtual desktops with both graphical apps and CLIs (xterms of various sizes) liberally placed thereon.<p>As such, there is no obvious incentive to use a GUI and no obvious incentive to use a CLI. I believe I tend to use the right tool for the right job. So it is natural to start up a GUI app when images are required.<p>When it doesn't matter whether a particular image is supplied, I generally use a CLI. Because I don't need to 'fire up' yet another standalone program, it's 'cheaper', both in effort and also in start-up time, to simply use the nearest xterm.<p>In effect, one xterm can take the place of maybe half-a-dozen different apps, as well as being more convenient for me.<p>Jobs which need to repeated more than once a week can be stored as CLI scripts which can be invoked with a single word or, better again, called by 'cron' automatically. Try doing that with a GUI.
> I remember when I was first on-boarding with AWS S3 and EC2 back in 2006 they only had an API and CLI, no GUI dashboard. CLI seemed to be on equal footing with API in those days, but as the popularity of web APIs grew, the CLI didn’t seem to keep up.<p>What limitations did he find with the CLI?<p>Have been using CLI regularly at work for 10+ years and CLI is always there so I don't understand the comeback.