And honestly speaking, merely hours of using vscode was enough to convince to use better tools to do my job, nothing wrong with that.
These days I do nearly every other kind of development, and on several different platforms. I still believe macros are the most magical things you can every touch in any piece of tech. Nearly my whole career is basically writing ginormous quantities of Perl/Python/C over terminals, and I happen to be one of the heaviest users of vi(m)/emacs, on Solaris/AIX machines, then FreeBSD and now Linux. >I think you're coming from a place of strong familiarity with IDEs, but less familiarity with Vim. Along the way being knowledgeable enough to occasionally service the car. Installing it in vim is going on shopping spree for a car first, then using the car to go on shopping spree using that car. Installing a plugin in vscode is a one step process. You just explained the difference in this very statement yourself.
It's not as if I wrote Pylint myself, I added "dense-analysis/ale" to my config and I was done. >There's not much difference between installing LSPs in VSCode and adding plugins to Vim using Pathogen, vim-plug, or the built-in plugin manager. They don't add that much gains to your workflow in normal development scenarios. There must be little configuration work and things must work out of the box.Īnd lets be honest typing speed is not even relevant to software development speed so the editing efficiency gains in vim/emacs, while might save your day in heavy lifting text tasks via macros. To make vim/Neovim/emacs nearly as usable you need to reinvent these editing ideas but in the paradigm of modern day development workflow. Apart from bare minimal modal editing you really get nothing much. You have to keep moving between mouse and keyboard modes, formatting plugins like black for Python don't autoformat on save like they do on normal vscode editor. In cases where Neovim is plugged into thing like vscode the experience is less than seamless.
Hence the use is by and large restricted to one off server side editing(This itself is getting rarer these days with containers). To get Neovim kind of things to be anywhere near usable for modern day development work, you need to bolt a file browser, intellisense, command line section, remote editing section, container plugins, plugin installer, settings section etc etc on top of it, and is not really a trivial job for everybody to do this from scratch. Neovim and vim are just the editor component of the bigger tools that is something like vscode.
0 kommentar(er)
