They see the script as the end, when in reality it’s a foundation. I rarely look at my foundation. I build on it.
With this workflow I have dozens, hundreds, or thousand of automatic actions that “just work”. Idk, works for me.
That said, if you prefer to click yourself to RSI to accomplish the same task, who am I to judge. I just watch and nod until I’m asked for a suggestion.
i imagine a perfect world in which everything has guis and the guis contain all the information I could want about what it does including the relevant terminal commands. In this way, the gui is also the manual.
People complain KDE has too many settings and option while they are so much less than few cli programs combined. Imagine how cluttered that UI has to be
On CLI I figure out the command I need once.
Put it in a script.
Cron it if I want it to be daemonized.
Never think about it ever again.
Anti-CLI folks just have a bad workflow.
They see the script as the end, when in reality it’s a foundation. I rarely look at my foundation. I build on it.
With this workflow I have dozens, hundreds, or thousand of automatic actions that “just work”. Idk, works for me.
That said, if you prefer to click yourself to RSI to accomplish the same task, who am I to judge. I just watch and nod until I’m asked for a suggestion.
i imagine a perfect world in which everything has guis and the guis contain all the information I could want about what it does including the relevant terminal commands. In this way, the gui is also the manual.
People complain KDE has too many settings and option while they are so much less than few cli programs combined. Imagine how cluttered that UI has to be
a cluttered ui that works is better than a pretty ui that doesn’t.
I don’t disagree but some people hates that kde has a lot of options