3 ms·
I started on Vim, then moved to Spacemacs, then Emacs with Vim bindings, now on VScode with Vim bindings... honestly, a good IDE does a lot of things for develo
by Rainymood 7y ago
I started on Vim, then moved to Spacemacs, then Emacs with Vim bindings, now on VScode with Vim bindings... honestly, a good IDE does a lot of things for developer productivity.
We have to remember that, while we are defined by our tools, we are all still building the same thing: code. What your employer/boss/client cares about is /what/ code you produce and what business value it generates. They don't really care about /how/ you do it.
- nsomaru 7y agoI eventually moved away from vscode vim to nvim + lsp because the bindings weren’t good enough. Small things added up enough to just jar me enough that it wasn’t worth it. Maybe I’ll jump in there again when I need to refactor something in a big way but for me nvim+plugins are where it’s at.
- mpfundstein 7y agoWhy not just use vim with a proper setup? If you are proficient with the bindings and modal workflow, I don't really see a reason to use those bloated alternatives that not even run in the terminal... Everytime i try something else i wander eventually back to my little vim setup :-)q