News for hackers. Stuff that matters.
Re:Cakebrew: The Mac App for Homebrew by GuiA on Tuesday April 29, 2014 @03:10PM (#7669287)
> The engineering world would be a much better place if more people built beautiful, easy to use GUIs on top of the confusing command line apps we all rely on.

I'd correct that to:

The engineering world would be a much better place if more people built beautiful, easy to use command line apps

It can be done, although it takes a lot of effort to do well- and a lot of the developers who write CLIs* have very few notions of HCI design. As a result the vast majority of CLIs are inspired from programs that are decades old, and in which no thought was given to the interface, thus perpetuating the cycle.

When well executed, a CLI is insanely superior to a GUI on many fronts (with a few exceptions, naturally, such as image/video editing), and more respectful of the users. It is much more friendly to users with vision or motor impairments: any font and any color scheme can be applied, any method of text input can be used, text readers behave in a much more predictable manner, etc. And of course it enables scripting to a level that GUIs just can't compare to.

Ideally you'd have a well designed CLI for the users who want it & scripting, and a well designed GUI - but let's face it, doing both is a huge drain of time. If you're going to do one, then a CLI is much, much preferable.

On the usability scale, there isn't "CLI apps" on one end and "GUI apps" on the other. Some GUIs are extremely usable, some aren't; some CLIs are extremely usable, some aren't.

I am a staunch supporter of the idea that while GUIs became mainstream and CLIs were relegated to a niche position, it should have been the opposite. But we had mediocre CLIs and decent GUIs, so it's only natural that it went that way. Great CLIs would have been preferable on many fronts.

Traditionally, the main argument against CLIs is the lack of discoverability that GUIs afford, which is a very valid point. That being said, most CLIs don't make an effort to enhance discoverability, which makes the argument still valid, but a little unfair.

Ultimately, I fully subscribe to Jeff Raskin's argument that if you're going to build a tool that users will use on a daily or weekly basis, then it's better to build something with a steep learning curve the first few hours which then results in an efficient and effective tool, rather than something that any newcomer can master within seconds but that will be tedious for extensive use.

GUIs that you can master in seconds belong in smartphone apps that you will use a handful of times and then delete a few weeks/months later (this isn't dismissive- if there's a market for it, then it's legitimate). Powerful CLIs that are a bit rough the first handful of hours but become extremely powerful tool belong in your browser, your email client, your text editor, your calendar, and so on: tools that you expect to use for years, if not your lifetime.

* : In this comment, by CLI I mean any form of program that runs solely in a command line, but that also includes highly interactive apps built with ncurses etc. There are very, very few command line apps that are solely "type a command, get an output" anymore.

Re:Cakebrew: The Mac App for Homebrew by nardi on Tuesday April 29, 2014 @05:27PM (#7670060)
A toddler can pick up and learn to use an iPad in an hour or two.

That will never, EVER be true of CLIs, no matter how well designed.

Your perspective on this subject seems to be from an extremely narrow viewpoint that ignores the actual real world outside of your own use cases.

Re:Cakebrew: The Mac App for Homebrew by GuiA on Tuesday April 29, 2014 @05:53PM (#7670173)
A toddler also can't operate a letterpress, solder, or fly a plane. Your point?

There are designers who worry about designing for toddlers, but that's a very specific niche, not at all representative of the average computer user. Hence my comment was not concerned with designing software interfaces for toddlers. Of course I wouldn't advocate using a CLI for an application meant for toddlers.

(My perspective on the subject comes from someone with a graduate degree in HCI, papers published at major ACM conferences, and who has shipped dozens of interactive software titles in the past decade (including some that have, surprisingly, been destined primarily for toddlers). I'd love to pursue a constructive conversation, but your ad hominem makes it hard.)

Re:Cakebrew: The Mac App for Homebrew by nardi on Tuesday April 29, 2014 @06:20PM (#7670301)
I apologize—I suppose I am somewhat irrationally offended by your seeming disregard for the biggest advance in user interfaces in the history of computers, the graphical touchscreen. Especially considering your position as an expert. GUIs have made computing available to the masses—not just to experts—and that is incredibly important. And touchscreen interfaces have accelerated this advance.

> A toddler also can't operate a letterpress, solder, or fly a plane. Your point?

My point is that you are focused on a very narrow set of use cases (e.g. operating a letterpress, soldering, or flying a plane). For the vast majority of computing tasks, a (possibly touch-based) GUI interface is ideal. Yes, CLIs are better for some things, but those things are a tiny minority.

> There are designers who worry about designing for toddlers, but that's a very specific niche, not at all representative of the average computer user. Hence my comment was not concerned with designing software interfaces for toddlers. Of course I wouldn't advocate using a CLI for an application meant for toddlers.

But I take it from this that you WOULD advocate using a CLI for email, social media, shopping, instant messaging, reading a magazine, designing buildings/airplanes/computers, audio recording and production, data visualization, doing your taxes, operating points of sale, etc., etc., etc.

(And now I imagine that you will try to convince me that a CLI is actually better for one or more of those things. I am unlikely to believe you.)

GUIs are better, not because they are more efficient, but because they are intuitive. People can understand them, so they can actually use them effectively. Being able to use an inefficient tool is vastly better than being unable to use an efficient one. Focusing on intuitiveness has opened up computing to the entire human race, instead of just an elite few.

Re:Cakebrew: The Mac App for Homebrew by GuiA on Tuesday April 29, 2014 @06:53PM (#7670453)
The word "intuitive" is casually thrown around when talking about interfaces, and yet it has a very specific meaning in HCI, far from what most people believe. As posted in another comment: http://www.asktog.com/papers/raskinintuit.html

I don't deny that GUIs have their uses, and that there are certain use cases where they do outperform text-based keyboard-driven interfaces. But the reality is that those use cases are nowhere near as overwhelmingly numerous as GUI proponents make it out to be, and that for the vast majority of text driven tasks (including email, instant messaging, engineering work, doing your taxes, operating points of sale, etc.) they are superior in most regards. Note that I do not advocate abandoning all graphical tools on the computer - you're naturally always going to need an image editor, a video player, something to edit 3D models, etc. The framebuffer is always valuable; GUIs, not so much.

On top of that is the consideration that a lot of our computer use these days converges in the browser, which is a very unusual beast altogether. We originally designed the browser to view documents, and it has now evolved in a weird steam machine that does pretty much anything and everything. It's problematic, because the web is notable for being "disrespectful" of concerns such as accessibility to handicapped users. (note that the best citizens when it comes to such matters, such as Hacker News, Wikipedia, Reddit, and quite a few others, aren't that far off from purely textual interfaces)

Obviously it's going to be hard for me to convince you otherwise in a HN comment. That being said, if you have a genuine interest in the topic, I recommend that you read Jef Raskin's "The Humane Interface", and Ted Nelson's series "Computer History for Cynics". They're a good introduction that allows one to think about the design of computer interfaces independently from the GUI mindset that has imposed itself on the profession over the past couple of decades. The modern GUI (which is really Xerox Parc's GUI) is really not all it's made out to be, and there are many compelling things about the alternative branches (check out for example Plan9, for something completely different).

Re:Cakebrew: The Mac App for Homebrew by nardi on Tuesday April 29, 2014 @08:09PM (#7670765)
Xerox Parc's GUI changed the world in the Macintosh and Windows, bringing computing to the masses.

The iOS-like GUI changed the world again in the iPhone, Android, and the iPad.

The reason they did is that they were better. Not because they were pretty. You seem to be convinced that these paradigms were not massive improvements on their predecessors. I'm not sure how you manage to maintain that view.

What makes them better is that they are visual in nature. Human beings have an immense amount of latent machinery to help us deal with visual things. Literacy, on the other hand, is an incredibly recent phenomenon. Interfaces that are based on words for communicating semantics instead of primordial visual cues like space, size, contrast, color, movement, etc., will never be able to compete on intuitiveness/ease-of-use/ease-of-learning.

Re:Cakebrew: The Mac App for Homebrew by flohofwoe on Wednesday April 30, 2014 @08:02AM (#7672715)
Problem I have with most touch interfaces (and to a wider extent the whole closed iOS ecosystem) is that they still have to show how they actually improve productivity. So far all we've seen is dumbing down the "user experience", turning computers from a productivity and creativity device into a pure media consumption device, glorified TVs basically. This is much much worse then the BASIC home computers of the 80's.
Re:Cakebrew: The Mac App for Homebrew by rezistik on Wednesday April 30, 2014 @12:16AM (#7671573)
A CLI is more productive, generally while a GUI is more fun. They each have their own use cases. A CLI has an inherent learning curve no matter how great the API, a GUI requires physical interaction delaying potential working.
Re:Cakebrew: The Mac App for Homebrew by teacup50 on Wednesday April 30, 2014 @10:03AM (#7673335)
"Better" is a very subjective thing.
Re:Cakebrew: The Mac App for Homebrew by __david__ on Tuesday April 29, 2014 @06:35PM (#7670368)
I had the unique experience of growing up with a PDP-11 in the house.

I could load the disk drive, type in my username and run commands on the command line to run the pac-man game.

You're (a) underestimating toddlers, (b) overestimating how difficult the command line is.

People really just don't learn it because it looks scary and isn't full of colorful pictures.

Re:Cakebrew: The Mac App for Homebrew by nardi on Tuesday April 29, 2014 @06:53PM (#7670456)
> People really just don't learn it because it looks scary and isn't full of colorful pictures.

This is so obliviously insulting to non-experts. The truth is that we geeks will waste hours of our time learning an obtuse interface because we LIKE doing that, but most people don't have time for that kind of thing. It's not that they are scared of apps that don't have "colorful pictures." It's that they have GOOD TASTE and aren't willing to waste their time learning a non-intuitive interface. They'll take their business to someone who has more respect for their time.

Re:Cakebrew: The Mac App for Homebrew by __david__ on Tuesday April 29, 2014 @08:34PM (#7670860)
> This is so obliviously insulting to non-experts.

No, it really isn't. My point is that the command line isn't actually all that difficult. It takes a little more memorization up front, though that hardly makes it only for "experts" (but that seems to be how it mostly settles out in the real world).

I think many people consider the standard GUI to be self explanatory, but, having had to teach some older people how to use a Mac or and iPad, I've found it really isn't. It's only intuitive if you already know how GUIs should work—coming from nothing it's just as impenetrable as a command line prompt.

Re:Cakebrew: The Mac App for Homebrew by nardi on Tuesday April 29, 2014 @09:19PM (#7671013)
> No, it really isn't. My point is that the command line isn't actually all that difficult.

For you.

> It takes a little more memorization up front, though that hardly makes it only for "experts" (but that seems to be how it mostly settles out in the real world).

Hmmm, that pesky "real world."

> It's only intuitive if you already know how GUIs should work—coming from nothing it's just as impenetrable as a command line prompt.

Seriously? This is significantly overstating the case. Yes, you still need to learn some things to use an iPad. But the learning curve is orders of magnitude less steep than that of the Unix command line. The empirical evidence is against you here.

Try teaching those same "older people" how to read and respond to their email on the command line and see how far you get in the same amount of time.

Re:Cakebrew: The Mac App for Homebrew by filmgirlcw on Tuesday April 29, 2014 @11:08PM (#7671376)
This is true in the context of 2014, yes, but it's not necessarily historically true. My mom was basically computer-phobic before I got her an iPad in 2010, but in the '70s and early '80s, she was flat-out amazing on an electric typewriter and word processor. The word processor (a designated terminal, not a software package), was basically a really terrible command line with awful CP/M style menus and lots of complex key bindings. That, my mom could do. Windows 95-XP? Scared her shitless.

Another example. My mother-in-law worked at AT&T and then Bell South after the breakup for over 20 years. In the late '70s - late '80s, everything she did was on UNIX boxes. My husband literally spent parts of his childhood in data centers late at night while his mom did systems work.

My mother-in-law is very smart, but I still have to walk her through some stuff on a Mac or iPad. (And the Mac was a huge step for her, apparently she really struggled with Windows), yet at 74, this woman can still do UNIX commands and work in a shell in her sleep.

My late-Aunt was an engineer at CSX for 33 years. During the Year 2000 crisis, she was one of their senior COBOL leads (she got her CS degree in '74) and did a lot of the infrastructure work to fix those mainframes. But I remember her struggling with certain more "basic" computer skills, at least in the context of a Windows GUI.

It's about what you learn on. When I was in high school and college, I worked as a tech at a big box retailer, I would often have elderly people come in upgrading old machines, frustrated that they couldn't get the version if WordPerfect of Eudora or whatever to run on XP or whatever. Most of the time, those old programs were I intuitive by any standard, but it's what they knew.

If you grow up on a command line and continue to evolve what you use and try new apps, platforms and paradigms as they crop-up (which is the case for most if us here), you may not recognize the importance a first-system plays in future skills and usage, but it does. And that's why it's important to consider that the people growing up today won't enter a world where they type commands and wait for an output as SOP. Sure, some will learn those methods out of interest or for the efficiency that can provide, but people born today stwrt interfacing with systems very differently than we did generations ago, and that's why being aware of those paradigms is so key.

That doesn't mean you can't make something accessible that is CLI based - you can - but kids will enter pre-school knowing how to use an iPad -- and advanced usage too. It's the same way I was able to learn to program them VCR at 4 before I could read more than Dr. Seuss.

Our software needs to be accessible for them to use, because we're past the era of GUI being too expensice to program for or requiring too many resources.

Re:Cakebrew: The Mac App for Homebrew by ForFreedom on Wednesday April 30, 2014 @01:58AM (#7671835)
You have an IT Corporate there
Re:Cakebrew: The Mac App for Homebrew by __david__ on Wednesday April 30, 2014 @03:47AM (#7672062)
> Try teaching those same "older people" how to read and respond to their email on the command line and see how far you get in the same amount of time.

Again, you are overestimating the difficulty involved here. You type "mail" to enter the mail program. Then you hit the return key to read your next mail message. You can type "r" to reply, or "d" to delete it. Type "q" to quit.

It's really not that hard.

Re:Cakebrew: The Mac App for Homebrew by barbs on Tuesday April 29, 2014 @08:21PM (#7670818)
His original statement was:

The engineering world would be a much better place if more people built beautiful, easy to use command line apps

Toddlers are not part of the engineering world...

Re:Cakebrew: The Mac App for Homebrew by jpwagner on Tuesday April 29, 2014 @05:40PM (#7670111)
A toddler can learn an ipad true, but it should be clear to any parent that they understand a "command" far earlier. it's no wonder the first baby sign language phrases they learn are "more" and "all done".
Re:Cakebrew: The Mac App for Homebrew by flohofwoe on Wednesday April 30, 2014 @08:05AM (#7672731)
Problem is that iPads/touch devices in general don't scale up beyond non-toddler tasks. It's painful to watch someone do something simple as their email on an iPad. Even copy-pasting something from one app into another is hilariously involved.
Re:Cakebrew: The Mac App for Homebrew by nardi on Wednesday April 30, 2014 @03:05PM (#7675574)
Not as hilariously involved as doing the same thing on the CLI.
Re:Cakebrew: The Mac App for Homebrew by flohofwoe on Friday May 02, 2014 @04:50AM (#7684663)
Well, the simplest form of copy-paste on the command line is piping output from one command into another, just a single character '|'. But I was mainly talking about iPad-style single-window touch-control environments vs. keyboard/mouse multi-window desktops.
Re:Cakebrew: The Mac App for Homebrew by rmrfrmrf on Wednesday April 30, 2014 @05:19AM (#7672303)

    A:\> C:
    C:\> win
Re:Cakebrew: The Mac App for Homebrew by brianpgordon on Tuesday April 29, 2014 @03:42PM (#7669498)
I don't see why restricting yourself to an array of monospaced characters is necessarily a good thing. You can make an argument that keyboard control is superior to mouse control but there's no reason why a graphical app can't be controlled by the keyboard.

In fact, you can trivially make any existing interactive CLI app better by recreating it exactly in an X window and adding a few graphically intuitive elements like icons and nice rounded tabs/scrollbars. And you can use proportional fonts- it's been proven that humans can read proportional fonts more quickly than fixed-width fonts.

https://i.imgur.com/WAmklLE.png

Re:Cakebrew: The Mac App for Homebrew by userbinator on Tuesday April 29, 2014 @10:10PM (#7671192)
I think the best UI is a CLI-GUI hybrid; it has all the features of a GUI, so you can point and click if you want, but also a CLI you can type commands in. AutoCAD is one of the few examples of this that I think got it right; on the other hand, Photoshop is one of the applications I use regularly that could really benefit from having a CLI.
Re:Cakebrew: The Mac App for Homebrew by mh- on Wednesday April 30, 2014 @03:07AM (#7671974)
do you have other examples of GUI apps that have attempted this? (even if they didn't do a great job)

I just find this topic interesting. I haven't used AutoCAD in many years, so don't remember what it looks like at all. :)

Re:Cakebrew: The Mac App for Homebrew by userbinator on Wednesday April 30, 2014 @06:05AM (#7672419)
The only other example I can think of are file managers (e.g. http://docs.kde.org/stable/en/applications/konqueror/cmndlin... ); CLI-GUI hybrids are definitely quite rare.
Re:Cakebrew: The Mac App for Homebrew by jsmeaton on Wednesday April 30, 2014 @08:51AM (#7672918)
Pretty much any IRC application?
Re:Cakebrew: The Mac App for Homebrew by Tloewald on Tuesday April 29, 2014 @07:32PM (#7670619)
The world would be a better place with both better command line apps and beautiful graphical front ends. The former makes doing the latter easier, while the latter also allows you to work easily with the less wonderful command line apps.

> Traditionally, the main argument against CLIs is the lack of discoverability that GUIs afford, which is a very valid point. That being said, most CLIs don't make an effort to enhance discoverability, which makes the argument still valid, but a little unfair.

That's only one argument against command line apps. There's also ease of use, progressive disclosure, learning curve, the relative ease of recognizing and remembering versus memorizing, and so forth.

Re:Cakebrew: The Mac App for Homebrew by ckuehl on Tuesday April 29, 2014 @03:58PM (#7669589)
Out of curiosity, can you provide an example (or examples) of what you consider to be a well-designed CLI?
Re:Cakebrew: The Mac App for Homebrew by brian_cloutier on Wednesday April 30, 2014 @03:40AM (#7672040)
I would like to suggest mitmproxy as a well-designed CLI. It is a dream to work with and takes a little bit of effort to learn how to navigate but afterwards you fly around effortlessly.
Re:Cakebrew: The Mac App for Homebrew by GuiA on Tuesday April 29, 2014 @04:05PM (#7669629)
There's no perfect example, but if all CLI apps had as much thought put into them as there is in Midnight Commander, then I think we'd be somewhere fairly good :)
Re:Cakebrew: The Mac App for Homebrew by Osmium on Tuesday April 29, 2014 @05:12PM (#7669979)
I confess, I've never used Midnight Commander, so I thought I'd be a good guinea pig. I just installed it on my Mac and I don't find it at all intuitive. Two specific issues I had is that we're limited to displaying everything as text (e.g. what is ".[^]>" meant to represent? if it were a graphic, perhaps it'd be easier to understand), and also there's limited space in my terminal so commands are abbreviated (what does 'RenMov' mean? I can't 'mouseover' it to find out more information either–there's no way to interact with the app that might not also issue a command). Overall, it's left me with a vague anxiety I might accidentally delete a file.

This isn't meant to be a criticism of Midnight Commander anymore than it is a criticism of myself as a user. I have no doubt it's invaluable in certain situations. But I do think GUI apps offer clear advantages, and they're to be embraced.

Perhaps better would be the idea that all GUI apps should have lightweight CLI counterparts, to enable easier scripting/integration with a UNIX workflow, and be done with. OS-level scripting support is halfway there (e.g. AppleScript) but it could be better.

Re:Cakebrew: The Mac App for Homebrew by GuiA on Tuesday April 29, 2014 @06:17PM (#7670288)
I agree with you that mc is far from perfect.

That being said, its goal is not to be 100% usable out of the box without reading any documentation. Rather, the goal is to offer a tool that, after a few hours of learning, can be used extremely productively and efficiently for the rest of your life. I have yet to see a single GUI file explorer that offers something that mc couldn't (and for that matter, I have yet to see a single GUI file explorer that offers a level of functionality anywhere near mc - for many features in mc, a GUI driven interaction would be detrimental to the tool).

Also, one thing to keep in mind when talking about interfaces is that "intuitive" is a very tricky word that doesn't necessarily mean what we'd like to think it means: http://www.asktog.com/papers/raskinintuit.html

---

To answer your specific point pertaining to mc:

> there's no way to interact with the app that might not also issue a command). Overall, it's left me with a vague anxiety I might accidentally delete a file.

You can press F1 for context sensitive help (you can also click on any interactive element in mc, if you really want to use your mouse!). And of course, every destructive action asks for user confirmation before being committed.

Thoughts like "what does 'RenMov' mean?" are totally normal (and also occur with GUIs for sure) - but knowing the answer takes you 30 seconds, and then you're set for life. Again, when you're considering the fact that this is a tool you're likely to use for thousands of hours over your life if you commit to it, it makes it a worthy investment. Sure, the OSX Finder doesn't take a few hours to understand - but the huge amount of time lost doing things in Finder.app (or explorer.exe or dolphin or nautilus or ...) that can be done in mc much faster pale in comparison to that learning curve.

Re:Cakebrew: The Mac App for Homebrew by pessimizer on Tuesday April 29, 2014 @06:29PM (#7670348)
A Curses GUI is still a GUI. Midnight Commander is a GUI interface to the file system that I only install when my mother has to shell into my server (it is definitely a good GUI, though.)
Re:Cakebrew: The Mac App for Homebrew by dragonwriter on Tuesday April 29, 2014 @06:35PM (#7670374)
> A Curses GUI is still a GUI.

No, a curses-based UI is a text-based UI, not a graphical UI; it is distinct both from GUIs and from CLIs. It does share some characteristics with GUIs, sure.

Re:Cakebrew: The Mac App for Homebrew by billyhoffman on Wednesday April 30, 2014 @12:26AM (#7671603)
I'm confused GuiA. You have spent considerable time and energy promoting your view that well designed CLI apps are "insanely superior", but you can't cite an example? And the closest thing you cite, MC, is a text-based GUI?