Thanks! It's not that vscode is bad and yes there are some other amazing features like the remote connect offering, and live share.
For me I use nvim as my daily driver because I work in a terminal all day. And I find it fun to tweak things here and there as needed.
I do follow your word of caution that one can go down a hole of wasted time with config tweaking. And the whole point of learning vim, is that's it's installed on more servers. So if you need to hop on a machine and check it out you can. But that defeats the purpose of this article, because once you configure vim this way, it's not vanilla any more.
So I tinkered with vscode for a bit, and there is just as much config with it as there is vim. With less flexibility. Going to stick with vim. Thanks for the thoughts though.
Thanks! It's not that vscode is bad and yes there are some other amazing features like the remote connect offering, and live share.
For me I use nvim as my daily driver because I work in a terminal all day. And I find it fun to tweak things here and there as needed.
I do follow your word of caution that one can go down a hole of wasted time with config tweaking. And the whole point of learning vim, is that's it's installed on more servers. So if you need to hop on a machine and check it out you can. But that defeats the purpose of this article, because once you configure vim this way, it's not vanilla any more.
Thanks for your comment.
Agreed.
I am a big fan of vim/nvim and I am using vim for 10 years.
Recently, when I looked back, I was (wasting) a lot of my time in trying out new configs just for the fun of it.
And decided to stick to vscode as the main editor, ofcourse with
vscode-vimextension :-)So I tinkered with vscode for a bit, and there is just as much config with it as there is vim. With less flexibility. Going to stick with vim. Thanks for the thoughts though.
@casonadams I would love to see your work in your vim config.
Have you made any videos?