Even if you just learn less than 10 keys/shortcuts, you'll be way more productive with vim. Usually I work in an IDE, but I also use SSH a lot so when I go into a server that does not have vim it sure is a pain.
@ivanyv I guess I misunderstood the context of using Vim. I have only ever used vim on a machine on the same network. I have never developed on a server I could actually touch so I use putty to talk to the server, which I guess I use vim on putty. but I also use WinSCP when I would rather use a text editor on my local machine like sublime or codeyourcloud if I want to save a copy of the files in google drive.
I would much rather edit my files in sublime than in a text editor like Vim which to me seems tedious to downright archaic in terms of modern editor technologies.
@mjwrazor gotcha, though I think maybe you're a bit confused. SSH is a protocol not an app, the apps you mention work over it, and I guess you actually need those in Windows. Mac/*nix systems are different in that regard. And not to start a flame war, but vim is anything but archaic (pretty much as powerful as Sublime, though both have their advantages
obviously).
@ivanyv You make a good point and yes I was confused. Also you press the use of vim so heartedly maybe I didnt dive into the editor as much as I should have. It could of been the professor who taught us only touched on fundamentals. Which I wouldn't be so surprised since every class seemed rushed. Il have to take a second look.
@mjwrazor glad to be of help. Learning vim fully takes a lot of dedication to be sure, so might not be worth your time. Like I mentioned in my answer, if you get familiar with a few keys/shortcuts, it will be all you need to always choose vim over nano. It's been years since I used vim as my main editor (I mostly use an IDE now), but whenever you SSH into a server it's a timesaver.