GUI > CLI but a CLI is still necessary/useful as Arkhan pointed out well enough and better than I felt like doing. The GUI provides you with a CLI when you occasionally need it, so what's the discussion ? You seriously would prefer that the OS, in principle/by default, be controlled/interacted with mainly via a textual interface ?? Or what, you like taking the counter-intuitive position on a no-brainer and baiting folks ? 
I don't regret my DOS-only days, but I'd never wanna go back to 'em...
I'm gonna whole-heartedly disagree here on your generic GUI > CLI. GUI is better for casual computer users, and for casual computer interactions, but keyboard-driven input will always be faster for expert users, be it well-designed shortcuts or a CLI. That's the thing, though, CLI is not for novices. It requires memorization and familiarity, but once you have it you are inherently faster than any GUI user at a wide variety of tasks.
It's a widely held adage that a *nix system admin will spend 2 hours making a script that simplifies a 5 minute task even if he only uses it once. I don't doubt that it can be faster, but if it requires memorisation and familiarity, is it worth it for things you seldom do?
Here's a story which is actually counter-supportive to my argument, but I was told early on; don't rely on fancy programs, and don't create a bunch of scripts to make your life easy. Some of the best advice I ever had. Because Unix is so old, most systems share a lot of basic commands and structures, so if you learn those basics, you'll be able to work on nearly any *nix OS.
Anyway, this guy I worked with was a proper Linux nerd, while our main OS was FreeBSD. He decided his workstation (which like every workstation was actually some kind of server for something else too, mine was the webserver, it was a small company) could do with an update, so he started messing about with shared libraries, installing his favorite bullshit programs he used at home.
Long story short, he messed around with some serious shit, and ended up dicking the machine to the extent that fstab got wiped, or it couldn't find it or whatever, which is pretty serious when you have a server like that. Guy came up to me white as a sheet and asked me for help, because he didn't have access to any commands less than 20 years old.
Took me about 10 minutes, but using my fstab as a reference, I managed to cat the whole fstab back from the command line and boot his machine back up, and no-one was any the wiser.
I use that story a lot in job interviews.
But STILL, if I have a GUI, I can have multiple putty sessions. This alone renders any argument against GUI null. I can copy and paste config easily from one box to another way faster than editing an existing file, scping it, closing down that session, opening another and blah blah blah however many times before I get it right.
It's like bowl vs ice cream when the ice cream comes with a f*cking bowl
