Live data from Hacker News

The Command Line Challenge.

blog.chavezgu.com

11–20 of 45 posts

Re: The Command Line Challenge.

#11
My (unintentional) Command Line Challenge was trying to build Gentoo on a 100MHz laptop with no other computers around. That was about 2 days of compute work. At the time, it didn't compile reliably either, so emerge would crash 5-10 times while trying to get to Xorg. Learning to fix the problems, particularly via lynx, brought me up to speed more quickly than anything else.

Something to be said for leaning by immersion.

Re: The Command Line Challenge.

#12
post #6

More like "the terminal challenge." Curses-based programs (like vim, mutt and lynx) still have graphical user interfaces, they just have really shitty graphics. (And that's not a criticism of those programs.) Try spending a week using just ed, mail, and curl. Those are actual command-line programs, not just terminal-based programs. The litmus test is whether they would work with a real paper teletype.

  "When I log into my Xenix system with my 110 baud teletype, both vi and Emacs
   are just too damn slow. They print useless messages like, ‘C-h for help’ and 
   ‘“foo” File is read only’. So I use the editor that doesn't waste my VALUABLE time.

   Ed, man!  !man ed"
http://www.gnu.org/fun/jokes/ed.msg.html

Re: The Command Line Challenge.

#13
post #6

More like "the terminal challenge." Curses-based programs (like vim, mutt and lynx) still have graphical user interfaces, they just have really shitty graphics. (And that's not a criticism of those programs.) Try spending a week using just ed, mail, and curl. Those are actual command-line programs, not just terminal-based programs. The litmus test is whether they would work with a real paper teletype.

Curses-based programs (like vim, mutt and lynx) still have graphical user interfaces, they just have really shitty graphics. (And that's not a criticism of those programs.)

I'd say the keyboard-centricness still separates them from, say, Eclipse.

Re: The Command Line Challenge.

#14
post #13
post #6

More like "the terminal challenge." Curses-based programs (like vim, mutt and lynx) still have graphical user interfaces, they just have really shitty graphics. (And that's not a criticism of those programs.) Try spending a week using just ed, mail, and curl. Those are actual command-line programs, not just terminal-based programs. The litmus test is whether they would work with a real paper teletype.

Curses-based programs (like vim, mutt and lynx) still have graphical user interfaces, they just have really shitty graphics. (And that's not a criticism of those programs.) I'd say the keyboard-centricness still separates them from, say, Eclipse.

[deleted]

Re: The Command Line Challenge.

#17
Amusingly, Emacs can do pretty much all he listed. Of course, as somebody who pretty much lives in Emacs and a browser, I'm probably the wrong demographic :).

Also, I'm annoyed at other commenters' equating "command line" with primitive: just because GUIs are newer does not mean they are superior or that the command line is obsolete! For a large range of tasks like file management or system administration it is actually superior; for quite a lot of other things it's completely usable. I'm not saying GUIs are useless or that the command line is perfect for everything, but it is far from obsolete or inferior.

Now, doing everything in a terminal is overkill, which is why this is a challenge--you're not expected to use a terminal forever, just long enough to get sufficiently acquainted with it so that when you do things the terminal is great at--which you will--you will be able to use it as efficiently as possible. And, since all the readers here doubtlessly spend very large amounts of time behind a computer, being as efficient as possible there should be a priority.

Coincidentally, I say all this as somebody who started using a computer with Windows 95. I only learned how to use the command line (first a bit on Windows then on Linux) because it looked cool; I continue using it because it turned out to be more efficient at a whole host of tasks than using a GUI.

Re: The Command Line Challenge.

#18
CLI is great from *NIX perspective and I believe most of us had used it extensively in the past. I still use CLI but if and only if it suits as the best tool for the problem I'm working on. The fact is, that the paradigm has changed, therefore the way we interact with our computing devices.

IMHO, bigotry is not only bad in politics. We have to embrace the change, learn new tools, improve, share our knowledge and not only make our jobs better for ourselves, but also for others. Especially for rookies, who will have to be doing more tomorrow than what we do today. I don't believe `libcaca` has anything to serve this purpose.

Using mutt instead of gmail; I'd ask "Why?". We don't need to stick with the tools we've used 10 years ago. If I'd be looking for a challenge as a sysadmin, I'd learn ways to better utilize cloud environments, look for better ways to serve static content for large volume systems, improve my tool base for managing geographically distributed servers, learn about the requirements of the new era of real time web, how to deploy node.js on my servers, etc.

Re: The Command Line Challenge.

#19
I use a lot of command line tools these days, but I always use a web browser for browsing the web and a proper music player too. I don't think "going cold turkey" from the GUI is really a good idea.

Both have their place.

Re: The Command Line Challenge.

#20
post #13
post #6

More like "the terminal challenge." Curses-based programs (like vim, mutt and lynx) still have graphical user interfaces, they just have really shitty graphics. (And that's not a criticism of those programs.) Try spending a week using just ed, mail, and curl. Those are actual command-line programs, not just terminal-based programs. The litmus test is whether they would work with a real paper teletype.

Curses-based programs (like vim, mutt and lynx) still have graphical user interfaces, they just have really shitty graphics. (And that's not a criticism of those programs.) I'd say the keyboard-centricness still separates them from, say, Eclipse.

For those looking for a keyboard-driven browser, try http://conkeror.org/
Post reply on HN