Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
That used to be true about 7 years ago, but now it's patently false. Many modern distros are highly GUI-driven. You don't need the terminal or command-line knowledge to install anything. You need the terminal about as much as you need Terminal on OS X.
That really depends on how you define 'need'. I desperately need the terminal in OS X for three simple reasons: (1) to look extra geek in front of ordinary GUI users, (2) to play around with predominantly command-line applications like GnuPG, and (3) because if GUI is a painting, terminal is poetry.
 
That really depends on how you define 'need'. I desperately need the terminal in OS X for three simple reasons: (1) to look extra geek in front of ordinary GUI users, (2) to play around with predominantly command-line applications like GnuPG, and (3) because if GUI is a painting, terminal is poetry.

That's why I said that you "need" the terminal about as much on OS X. :D

For me, that's "a couple times an hour" -- but that's because my job requires me to use SSH, gcc, etc. on a regular basis.
 
Sigh.

Did I say you could do the initial setup of a Linux box without using the command line?

No. I didn't.

Likewise, I'd never say that you can setup a Windows machine without mucking about with its internals, because for the most part that's just not true.

Thing is, for Windows it is true. An average user can install Windows, feed in the disks for each of their peripherals one at a time and use the GUI to install drivers, connect to their ADSL modem using the helpful CD with a Windows-based setup script, and be on their way. Whether that's due to Windows offering a superior experience or every software/device maker going out of their way to make things work better with windows is not really relevant.

For Linux, a lot of the people who make the software/drivers you use can't see an advantage to being able to do everything through a GUI. There might be a GUI that works most of the time, but that's not good enough: take package management. It's fine until you hit a problem it can't deal with, and then you have to drop down to running the dpkg stuff manually to sort it out. That's why I won't recommend Linux to any non-techie at the moment, as "Works with a GUI 95% of the time" is not enough.

Amorya
 
Thing is, for Windows it is true. An average user can install Windows, feed in the disks for each of their peripherals one at a time and use the GUI to install drivers, connect to their ADSL modem using the helpful CD with a Windows-based setup script, and be on their way.

Perhaps the "average users" that you've seen have possessed more knowledge than the ones I've seen. I have never, ever seen someone manage to go from a RTM XP disk to a fully-configured, fully-setup install with 100% functional hardware unless they were quite knowledgeable w/ regard to Windows administration.

For Linux, a lot of the people who make the software/drivers you use can't see an advantage to being able to do everything through a GUI.

Not true at all. I've been using *nix (in some form or another) for almost 15 years now. I'm quite familiar with command line usage, but I prefer a GUI for a lot of things -- some information is better presented in GUI form, and package names/descriptions are (in my opinion) some of those pieces of information.

There might be a GUI that works most of the time, but that's not good enough: take package management. It's fine until you hit a problem it can't deal with, and then you have to drop down to running the dpkg stuff manually to sort it out. That's why I won't recommend Linux to any non-techie at the moment, as "Works with a GUI 95% of the time" is not enough.

Oh come on now. At this point you're basically saying "Yes, there is a good GUI -- but you might run into something you can't solve with point and click!" Well... yes. That's the case for every desktop OS out there.

I could say the same about OS X, actually. OS X is great, unless you need to flush your DNS cache, and then you have to drop down to running the dscacheutil stuff manually to sort it out. That's why I won't recommend... etc.

The command line isn't some great evil -- it's a powerful tool, but it's one that's mostly unnecessary on modern Windows, Linux and Mac OS X desktops. From time to time, be it for troubleshooting or setup purposes, some folks may need access to it -- but by and large, on all three systems the average user does not. I really don't get this whole "the command line is sacred and must never be needed by anyone ever" thing... Sure, you shouldn't need it for daily tasks, but not all problems can be solved with a fancy GUI. Objecting to the use of an OS on the basis that there might, at some point, be something that someone can't handle by clicking a button is silly.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.