Linked by Thom Holwerda on Tue 3rd Jun 2008 17:47 UTC, submitted by ohxten
It's an ever-continuing debate: what is better, a graphical user interface, or a command-line interface? Graphical user interfaces may be easier to learn, but complicated operations may require a lot more user input than with a command line interface, which can perform several complicated operations by using a short sequence of words and characters. However, a CLI has a much steeper learning curve than a GUI. Google has always had a certain CLI-quality to it, and Stefan Grothkopp decided to take this a few steps further: say hello to Goosh.
Permalink for comment 316870
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-12-31
My first thoughts were: Why use a separate shell for this? Why not write a set of command-line tools that can be used in an existing shell?
I could imagine two reasons. The first is that simple command names like "google" or "translate" aren't exactly common in today's command line environments. Few people would ever dare bind a command like "translate" to google services because, "well, people may want to use another translation service, and we also want to give it a cooler name". Ironically, in the old days of the command-line, such a kind of simplicity was much more common.
The second reason is that Goosh outputs hypertext (e.g. embedded links), for which typical command line environments like bash (let alone Windows's cmd.exe) are not prepared.