I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
While I won't say Vim is the best, I think it does enforce a different paradigm of thinking that is beneficial to growth as a developer. It helped me think about concepts differently and got me to deep dive on Linux to really start to understand OS level things. (files, processes, etc)
That said, VSCode with VIM bindings is hard to beat.
My crazy workflow right now is have the main app open in VIM and VSCode. Do most of my coding in VIM, when I need to actually debug something, go to VSCode. Use all the tools :D
// , “It is not so important to be serious as it is to be serious about the important things. The monkey wears an expression of seriousness... but the monkey is serious because he itches."(No/No)
I keep forgetting they have this. One day my deep suspicions of Microsoft will wane enough to use it. Today is not that day, nor is tomorrow. But these little reminders bring it closer.
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
If I'm using Vim and want to switch to VSCode (I use VSCodium here) then I hit up the mapping and boom, there it goes. This is most useful when I want to use the debugger, which is sometimes easier in VSCode than it is in Vdebug.
// , “It is not so important to be serious as it is to be serious about the important things. The monkey wears an expression of seriousness... but the monkey is serious because he itches."(No/No)
"Hahaha", he says, clicking the little heart icon, while secretly knowing in his heart that Vim is still the best.
While I won't say Vim is the best, I think it does enforce a different paradigm of thinking that is beneficial to growth as a developer. It helped me think about concepts differently and got me to deep dive on Linux to really start to understand OS level things. (files, processes, etc)
That said, VSCode with VIM bindings is hard to beat.
My crazy workflow right now is have the main app open in VIM and VSCode. Do most of my coding in VIM, when I need to actually debug something, go to VSCode. Use all the tools :D
I keep forgetting they have this. One day my deep suspicions of Microsoft will wane enough to use it. Today is not that day, nor is tomorrow. But these little reminders bring it closer.
I use it like that. In fact, and I know this is getting 180-degrees from the point of the post, but I have this in my config:
If I'm using Vim and want to switch to VSCode (I use VSCodium here) then I hit up the mapping and boom, there it goes. This is most useful when I want to use the debugger, which is sometimes easier in VSCode than it is in Vdebug.
I would expect nothing less of such a gentleman and a scholar.
Oh my gosh, how did I not know about VSCodium. Thanks and that vim key remap is glorious!
My thought is that whatever tool makes development easiest for you is the best tool. (Full disclosure: I'm a huge fan of Visual Studio Code.)