Linked by David Adams on Fri 5th Aug 2011 16:08 UTC
Graphics, User Interfaces A couple of days ago I read a blog post by Stephen Ramsay, a professor at the University of Nebraska-Lincoln and a Fellow at the Center for Digital Research in the Humanities. In it, he mentions that he has all but abandoned the GUI and finds the command line to be "faster, easier to understand, easier to integrate, more scalable, more portable, more sustainable, more consistent, and many, many times more flexible than even the most well-thought-out graphical apps." I found this very thought-provoking, because, like Ramsay, I spend a lot of time thinking about "The Future of Computing," and I think that the CLI, an interface from the past, might have a place in the interface of the future.
Permalink for comment 483866
To read all comments associated with this story, please click here.
RE[2]: Two distinct beasts...
by WorknMan on Fri 5th Aug 2011 19:36 UTC in reply to "RE: Two distinct beasts..."
Member since:

To the extent that GUI are inherently a superset of CLI, then in theory GUI should be every bit as good as CLI.

Well, GUI is not inherently a superset of CLI - it's a COMPANION. Meaning, each is better at some tasks than the other, so they go together like sugar and kool-aid, and I wouldn't be without either. Why must everything be turned into a pissing contest?

When it comes to GUIs, some have said how it's easier to pull up files in a CLI, like when you need to copy all files that are older than a certain date and with a certain extension. But what if you need to copy about 50 random files from a directory of 300 files that don't have any specific pattern to them? In that case, it's easy to CTRL+CLICK select the ones you need and drag them wherever. Similarly, the article mentions how it would be easier to manipulate music playlists, but what if you've got a playlist with 300 songs, and you want to custom sort them? Again, it's going to be easier to just drag stuff where you want them.

Of course, one could list dozens of examples were CLIs would be more useful... as I said before, it's not about which one is 'better', because that depends on the context.

However in practice GUI programs are incredibly difficult to automate.

Actually, no it isn't... at least on Windows, it's quite easy:

The only exception to this is if apps don't use standard widgets, which is one of about 486472343 reasons why I'm a fan of standards in this regard. Of course, on Linux, this would never work, since the general assumption seems to be that having 900 different toolkits is a good thing. So if GUI automation is hard, it's probably because of a piss-poor implementation, or someone hasn't written the tools to do it. But doesn't that work the same way on CLIs? I mean, SOMEONE has to build in pipes and stuff if you really want to do something useful with it ...

Reply Parent Score: 4