3 ms·
I'm a long time vim user who's switched mostly to Atom(at least for bigger projects, vim is still my "quick fix" editor). Last time I tried VS Code(6ish months
by bsharitt 11y ago
I'm a long time vim user who's switched mostly to Atom(at least for bigger projects, vim is still my "quick fix" editor). Last time I tried VS Code(6ish months ago?), I liked it all right, but stuck with Atom because at the time the availability of vim like bindings was weak and ruby support was lacking.
- ngrilly 11y agoWhat made you switch from vim to Atom?
- bsharitt 11y agoMostly tried it and got used to it. I liked the defaults a lot more than I do vim(nothing some plugins, a good .vimrc, etc can't fix), and I found it much more natural to use extensions that I ever did vim, so once I got Atom matching my usual vim setup I found myself extending beyond that. Most of it's probably stuff I could do in vim too, but adding extensions on whim feels a bit more natural in Atom. I still spend a lot of time on remote systems, so vim is a big part of my tool box. There's also the weight of Atom. If I'm working on big project, I get it all loaded up and work in Atom, but if I just need to tweak a thing or two in a file, vim is still my go to.
- ngrilly 11y agoThanks for replying. I asked because so much people say "If you're serious about development then you need a serious editor: you should learn vim/Emacs because it's a once in a lifetime investment that will boost your productivity beyond what other tools provide". This mantra doesn't match my own experience. I think Atom and VSCode provide 3 main advantages over vim: the out of the box experience is better; using a GUI offers a more powerful user interface; extensions are easier to install and work better. It's like comparing fish and zsh: Atom and VSCode are more like fish; vim and Emacs are like zsh.