zlacker

>>james2+(OP)
I really want to like Sublime (it's so fast, I like the minimal UI), but VS Code has so much inertia, and does so much out of the box or with minimal extra effort that it's hard to not use it instead.

At the end of the day, I have things to get done, I'm not here to tinker with tools. Same reason I never got into vim/emacs etc as a daily driver.

>>dkdbej+Zg
Emacs and Neovim are things one gets into in ones free time and gets good enough to make the switch at some point at the job. Of course that is mostly only feasible, if the projects at the job are set up in a tool agnostic way or choice exists in the first place.

I also want to like Sublime, but I already have a well configured Emacs and I like using free/libre software. While Sublime was great when I used it in the past, I am not sure I would use it much, since I use Emacs all day now. But the reason for Sublime over VS code is, that it is way less bloated and not running in a browser. Would need to see a direct comparison, but wouldn't be surprised, if it showed to be way snappier. If one does not need lots of specifically VS code features, I think Dublime gets out of ones way and lets you get shit done.

>>zelphi+tj
> Emacs and Neovim are things one gets into in ones free time and gets good enough to make the switch at some point at the job.

I'd probably never end up proficient with vim (and today neovim) if I didn't do the complete opposite of this and forced myself to use it for real work directly. True, I went a bit slower for one/two weeks, but if you really have to use something foreign for most of your work, you'll learn it really quickly, as long as you're up for looking things up as you go along. Of course, YMMV and all that yadda yadda.

>>diggan+gH
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.

>>mufasa+IT
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.

>>tcoff9+h81
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.

>>mufasa+FK4
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.