> they often require more resources, are less powerful and hard to automate via scripting That's not a problem with the GUI paradigm, that's a problem with the

> they often require more resources, are less powerful and hard to automate via scripting That's not a problem with the GUI paradigm, that's a problem with the current implementations of it. Current implementations of CLI/TUI programs have many problems themselves: lack of undo, poor discoverability, low intuitiveness, no previewing (e.g. in the equivalent to file browsers), poor documentation (which makes the discoverability and intuitiveness problems worse), and so on. Moreover, with that context, > require more resources ...is a very poor reason to use them. Computers are meant to be useful, not to sit there saving compute/RAM/electricity. (I shouldn't have to add this here, but: obviously, if you have two identical tools but for the fact that one consumes less power, then of course I would say you should use the latter one - this is not that scenario)