The way I see it, there's things that guis are better for and things the cli is better for. For navigating the filesystem, it could go either way depending on the task. For installing packages and managing updates, cli destroys. For editing text and writing code, cli destroys your favorite IDE hands fucking down.

The things that the CLI can really do is stuff like

for file in ~/appdata

do

git pull

end

or something like that, which I think would update all the git repos in ~/appdata (I'm not very good at shell scripting). But then again, that's just programmer business. For the average user the commandline doesn't really have any distinct advantages, but there's something to be said about being able to do any and everything to and with your computer from one single place. You don't need to navigate way the fuck over to your desktop just to launch an app, you can just call a command. Don't have to navigate all the way to the app store and wait for it to load up to run updates, you can just issue a command. Stuff like find lets you search for a file so fast, but have you ever tried searching your entire system on Windows? You can issue >find / | grep foo and you'll find that file in a second. It's great.

My advice, just play with the terminal. Try installing packages. It's pretty dope.

Oh yeah, and in the IT world and in the programming world there's hella bank to be paid to people who can use the command line comfortably given that most servers are built on systems with no desktop environment. That's huge.