[mufasachan]

I would be curious to know how you managed to do this. I really tried to do this but the tons of dev tools I am using was too much for transitioning to neovim for my daily work. Namely, I need a DAP, multiple dev tools (lsps, linters, formatters) because I work with several projects which do not have the same tools[^1]. Luckily, I do not mix multiple programming languages. Plus, I containerize all my dev env. There might be some elements missing, but the point is the number of tools is overwhelming and it makes me think that I should do the whole configuration/setup on my free time.

Did you face similar issues? If yes, how did you solve them? Or maybe your work does not need that much tools? Or you have been more minimalistic than me for the number of features to be included in the neovim configuration?

[1]: I work in R&D, I need to tweak and contribute in many papers code or different toolboxes/frameworks on top of the team projects.

[diggan]

> Did you face similar issues?

I don't remember what exact year I did the transition at, but around 2014 - 2016 I think. At the time I was working on a PHP Symfony application (and its frontend made with Backbone.js) powering Typeform, and I think this was right about when docker entered the scene, we were still using Vagrant with what I think was NFS syncing or something else dog-slow. But both Docker and Vagrant works fine with vim, as long as you have a generic VM/container setup, it shouldn't matter what editor you use, in my mind.

But before that I was using Sublime Text 2, with minimal plugins/extensions, so moving to vim was mostly getting used to moving around and manipulating text, using some very basic text-based autocomplete, before eventually migrating to a "proper" setup years later. Since then, I honestly haven't touched my config much, so I'm sure there are smoother/better ways now.

Since then, I've used (neo)vim to write JavaScript (+HTML+CSS), Ruby, Go, Python, Rust, various other languages, but mostly Clojure/Script. When trying out a new language, I find some (neo)vim plugin that seems suitable and try it out. If it works well, great, otherwise try another one.

[mufasachan]

Thanks for sharing your experience!

[tcoff91]

LSP and formatter were really fast to set up. I used kickstart.nvim to get started and lsp and formatter are already mostly configured.

DAP is trickier to set up but is doable. How often are you really debugging though? In the beginning just run both neovim and your ide and just switch when you debug.

Back when LSP wasn’t a thing I still used vim but would just switch to an IDE when I needed to go code exploring and needed to be able to jump to definition and stuff like that. Wasn’t a big deal and was worth it to use both tools because vim is such a superior method for editing text.

[mufasachan]

Thank you for your answer. Some code base have chaotic execution path through a monolithic code base (by design). So, for these code bases, I heavily rely on the debugger. But I like your suggestion to use both of them, I think it's a good way to transition slowly and efficiently.

[tcoff91]

Another good way to transition is to use your editor's vim plugin.

Pretty much every IDE has a vim plugin that's at least adequate. I've had good experiences with vscode, jetbrains, and visual studio vim plugins.