2 ms·

I've been a vim user for a long time. I switched to Atom despite its slowness because I finally get linter and autocomplete integrations that just work. Those h

I've been a vim user for a long time. I switched to Atom despite its slowness because I finally get linter and autocomplete integrations that just work. Those have always been a pain to set up for me in vim, and when you are switching between machines all the time, that quickly becomes tiring. I don't see a reason to stick with traditional vim for the majority of my work, since most other editors have plugins with a very good coverage of the core vim features/keybindings. EDIT: Oh yeah, and multicurors. I just remembered that they were also a big part of reason for switching. At least at the time, every implementation of multicursors in vim was broken in a very major way for me.

artursapek 9y ago
Re: multicursors, that's what macros are for.
- hobofan 9y ago
  Sure, you can do most things with macros, but I prefer the interactivity of multicursors. With macros I have to carfully plan out how the macro will affect all the different instances where I let the macro run, and if something goes wrong, I have to revert it and try again. With multicursors I also have to do some trial and error, but usually much less since I can immediately see how each step influences the text at all cursor instances, and revert it in a much more granular way. If I have to do some heavier processing for 100-1000+ lines, I still use macros, but for most cases in my day to day programming multicursors just feel better.