Linked by David Adams on Fri 5th Aug 2011 16:08 UTC
Permalink for comment 483839
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2007-04-17
If you think about it, any CLI is just yet another programming language. Sure, there are problems that can be easily solved by CLI. But to think that a text based approach will quickly solve all problem is a bit naive.
CLI is very good at being very specific about what you want, and more importantly chaining (e.g. pipes) existing tools to create a new procedure. Again, this is just yet another programming language...
But if everyone uses GUI nowadays, it's not just because they are too stupid to understand CLI. GUI can present multidimensional information much more easily, and the user can interact with it very intuitively. Think about Google Map on a touch based device, how do you do that in CLI?
Another example I can think of as a programmer is GDB versus Visual Studio Debugger. Another would be SVN CLI versus TortoiseSVN. Each time the GUI version presents the information in a better way to the user, and ironically also provides more features.
If you're looking for a quick procedural approach to solve a problem then CLI is great. If you have to deal with any form of multidimensional information that's not quickly and easily filtered, then no, CLI is not what you want.