ardms@lemmy.world to VIM - Vi IMproved@lemmy.sdf.org · 11 months agoThe future of Vimgroups.google.comexternal-linkmessage-square7fedilinkarrow-up143arrow-down11cross-posted to: [email protected][email protected][email protected][email protected]
arrow-up142arrow-down1external-linkThe future of Vimgroups.google.comardms@lemmy.world to VIM - Vi IMproved@lemmy.sdf.org · 11 months agomessage-square7fedilinkcross-posted to: [email protected][email protected][email protected][email protected]
minus-squaremryessir@lemmy.sdf.orglinkfedilinkarrow-up11arrow-down1·11 months agoGood to see that we are not rushing into unnecessary changes. Main reason why vim > neovim, to me.
minus-squarenickwitha_k (he/him)@lemmy.sdf.orglinkfedilinkarrow-up4arrow-down1·11 months 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-squarefeoh@lemmy.sdf.orglinkfedilinkarrow-up3arrow-down1·11 months 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.