Linked by Thom Holwerda on Mon 28th Jan 2013 22:38 UTC
Thread beginning with comment 550666
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Be careful what you wish for, you may get it.
by moondevil on Tue 29th Jan 2013 07:05
in reply to "RE[4]: Be careful what you wish for, you may get it."
Now, what I can't wrap my mind around is why there hasn't been more work on scriptable software that can work well with both interfaces and then some more, considering how anyone who designs modern GUI software also ends up creating a form of CLI interface in the backend code at some point.
Do you mean like ARexx on the Amiga, OLE Automation on Windows or AppleScript on Mac OS X?
RE[6]: Be careful what you wish for, you may get it.
by Neolander on Tue 29th Jan 2013 08:13
in reply to "RE[5]: Be careful what you wish for, you may get it."
Do you mean like ARexx on the Amiga, OLE Automation on Windows or AppleScript on Mac OS X?
That's the idea indeed, except that for OLE and AppleScript at least it seems to me that applications had to do a significant amount of extra work to make their functions accessible from scripts.
Edited 2013-01-29 08:17 UTC




Member since:
2010-03-08
Why has it to be one or the other ?
Shells are fine as a computer administration interface. They use up little system resources, make few assumptions about what works and what doesn't, are easily scriptable, and their commands can be trivially transmitted from one person to another.
GUIs, on their side, are generally more practical for everyday use. They allow for more advanced tasks, it's easier to find out how they work without piles of documentation, they make more efficient use of screen estate, and they tend to be more aesthetically pleasing too.
Now, what I can't wrap my mind around is why there hasn't been more work on scriptable software that can work well with both interfaces and then some more, considering how anyone who designs modern GUI software also ends up creating a form of CLI interface in the backend code at some point.
The way people currently end up creating dumb GUI frontends whose sole purpose is to feed a CLI interface, or give up on GUI or CLI altogether, strikes me as suboptimal. Especially when people subsequently end up creating nonstandard CLIs in an attempt to go beyond the limitations of a pure GUI approach, as with voice interfaces.
Edited 2013-01-29 05:33 UTC