You don't use it to open a single file for editing, though. Think of it as a lightweight IDE. Use it to open you folder project, which I do once every few days or even per weekly reboot. Once it's up and running - which takes about 5 seconds for my project folder to open on a MBAir - its plenty snappy for editing code.
For one-off file edits, like my .bash_profile, nginx conf etc., I still use a terminal-based editor, which is what I'd use on a remote machine anyway.
So I would have to use two different editors, customize both, get used to both? That doesn't make sense to me (to be fair, mostly because I rarely have the need for IDE). But if I had, why use a lightweight IDE instead of a "full" one (say Visual Studio, JetBrains *, ...)?
If you don’t need a ‘full’ IDE there’s a lot of mental complexity you can avoid by going à la carte (editor+plugins). It’s easier to add features you care about than learn about a bunch of stuff you’ll never use. That’s very subjective, of course.
