Well, you don't have to use vi or emacs. IDEs exist. I personally find Eclipse to be a huge pain in the ass for anything other than superficial Java maintenance, but it's there, and sometimes it's the right tool.

The command line will never die. It's precise. It works. If you don't know how to use it, you're not a programmer. End of story.

I think that, just as programming is becoming multi-lingual over the years, it'll be more important to be able to switch between (a) emacs/vi and the command line and (b) a read-only IDE for code comprehension/navigation. (I'm surprised Github hasn't taken that on, at least for the major languages.) IDEs are great when you're reading code but they become a mess when people use them to write it, or when IDEs become formally a part of the company developer environment. (Watch out if the latter happens.)

I think the low level will change more slowly than the high-level. For low-level, staples like C (and possibly Go) will remain in force. It's at the high level where the rapid change happens. Of course, this kind of change is good and bad. It's great when you're in charge and get to play with fun new tools, and it's horrible when you're a grunt and change is inflicted upon you by others.