ardms to VIM - Vi [email protected] • 2 years agoThe future of Vimgroups.google.commessage-square7arrow-up145arrow-down11cross-posted to: [email protected][email protected][email protected]
arrow-up144arrow-down1external-linkThe future of Vimgroups.google.comardms to VIM - Vi [email protected] • 2 years agomessage-square7cross-posted to: [email protected][email protected][email protected]
minus-square@[email protected]linkfedilink10•2 years agoGood to see that we are not rushing into unnecessary changes. Main reason why vim > neovim, to me.
minus-squarenickwitha_k (he/him)linkfedilink3•2 years agoI am a fan of both, personally. I like neovim for my dev box and vim for remote servers, where stability is a higher priority.
minus-square@[email protected]linkfedilink2•2 years agoSame here. I feel like this is one of the best power moves ever for Devops/SRE/Platrform engineering types who need to actually work on real live servers and can’t always drag their entire configuration corups around with them.
Good to see that we are not rushing into unnecessary changes. Main reason why vim > neovim, to me.
I am a fan of both, personally. I like neovim for my dev box and vim for remote servers, where stability is a higher priority.
Same here. I feel like this is one of the best power moves ever for Devops/SRE/Platrform engineering types who need to actually work on real live servers and can’t always drag their entire configuration corups around with them.