I’ve spent my Easter break customizing Neovim
I like this post, it reminds me a lot of when I started using vim &#x2F; neovim in university. I spent a lot of time learning nano, cramping my hands, and then eventually deciding to sit down and learn vi proper.<p>One thing I&#x27;m not so sure of though -- the justification for neovim seems to be partially due to needing a pretty recent version (at least newer than 0.5.0, for LSP features). There seems to be a big portion of vim users who seem to dump on neovim for one reason or another as some kind of meme, but I&#x27;m not sure that I agree about it being bloated or whatever. If I have to run Slack for work next to neovim &#x2F; vim, I&#x27;m pretty sure I know what is using the majority of my system resources... Anyways, back to needing a recent version of neovim: I think the author could probably get by with just regular vim + extensions if they didn&#x27;t use LSP stuff.<p>To be honest, I still haven&#x27;t really used LSP much, and most of my experience using similar features in other products (Intellisense in Visual Studio, whatever the equivalent broken thing in Xcode is called) is that it really was never that useful? Maybe I&#x27;m misunderstanding something and it&#x27;s just not good for me and my workflow, but I feel like a lot of newer devs seem to enable it and declare that they can&#x27;t work with anything that doesn&#x27;t support it. For a long time I&#x27;ve avoided such features since they often seem to have poor performance (Xcode&#x27;s version of such has definitely taken down a Macbook Pro on me before), or just generally don&#x27;t add much to the experience other than some coloured lines under parts of my code.<p>A good compiler (e.g. rustc) and corresponding linter for static analysis (e.g. cargo clippy) are actually pretty good on their own! This isn&#x27;t true for every language out there, and maybe that&#x27;s where LSPs are more useful - the Typescripts &#x2F; Pythons &#x2F; Javas of the world! I don&#x27;t know if I&#x27;m over-simplifying it though. Either way, I&#x27;m pretty sure my point is that whether you choose vim or neovim, it&#x27;s a great idea to sit down and spend a good chunk of time just getting better at using your tools. It&#x27;s the kind of exponential improvement that won&#x27;t even seem egregious a year down the line.