I don't agree with the implication that CLI/TUI tools necessarily 'complicate' your life. To the contrary, half of the appeal (namely of CLI programs) is that they allow you to accomplish certain tasks in a far simpler, automatable way, contrast to a GUI that would require a lot of "manual labor" to achieve the same thing. For instance, in a very simple example, I could effortlessly move every file with ".jpg" as the extension to another directory with a command like "mv *.jpg ~/destination". In most GUI file managers, I would need to click a button to sort by filetype, then drag my mouse to select those files, then open the directory I want in the sidebar or another tab, then drag the files over to the destination. Of course, much of the appeal of Unix-like systems is that command-line programs are small, focused, and chainable with one another, such that you can perform fairly complex tasks simply. Scaled up to programs like dmenu, you can even simply implement custom interfaces and menus for your system, and your imagination/use cases are the only limit.
In the case of TUI programs, the appeal is generally that they treat keyboard control as a first class citizen, and are extremely configurable and extensible. For instance, in my file manager, 'ranger', I have keybindings that allow me to quickly travel to any directory on my system–I can type 'gmb' as shorthand for 'go ~/Media/Books', for instance. Or, I have another keybinding that runs a command that uploads the file(s) I have selected to a file-hosting or pastebin-style website, then copies that link to my clipboard. With a typical GUI file manager, I'd have to tediously open up my browser, then navigate to the file hosting website, then upload the file, then copy the link. It's also got useful built-in commands, like a bulk-rename feature that allows you to open up all of your listed files in a vim buffer, and rename them all at once (Emacs can do something similar in dired), or a 'flatten-directory' feature that allows you to view several nested directories as one single directory.
In either case, I think hardware efficiency is just a side-benefit (although, it can be a very meaningful benefit if you're using older or underpowered hardware). It's fair to argue that you pass aPost too long. Click here to view the full text.