4 ms·
> There are plugins that, so far as I know, can do a lot of what an IDE can do I want to add that the converse is true too: there are a lot of plugins (for IDE
by gjulianm 4y ago
> There are plugins that, so far as I know, can do a lot of what an IDE can do
I want to add that the converse is true too: there are a lot of plugins (for IDEs) that do a lot of what Vim can do. I personally use the neovim integration for VSCode and it's really nice.
- Aachen 4y agoHave you used the real vim a lot in the past? More than a few days of trying it out, I mean. Probably you replied around the same time as I edited in: >> Try it for one month and see if you want to go back to standard editors. Odds are, you'll want the best of both worlds, start looking for vim key binding plugins in IDEs, and end up like me with missing vim after all because those keybind plugins are usually not so great It might just be me who got too used to vim bindings by now so that the suboptimal implementations are annoying. Or maybe the vim bindings in VSCode are particularly good, I haven't tried those. (I've tried them in real visual studio in ~2015 and it was so bad that I ended up using plain visual studio instead, then went back to plain vim on linux after my C# internship.)
- gjulianm 4y agoThe VSCode neovim plugin is really good because under the hood it's just using neovim to manage the buffer, so everything that works on Neovim works on VSCode. It's true that some plugins are suboptimal but the VSCode one (and the one for Sublime when I used it) are really good.