This video does not intend to persuade viewers to use Neovim but assumes an interest in making the switch from VS Code to Neovim. It outlines a personal journey and strategy for effectively transitioning to Neovim, highlighting the importance of initial difficulty, using the Vim extension as a transitional tool, and customizing Neovim for improved productivity.
Main Points
Step 1: Desire Check
Evaluate personal interest and desire to switch to Vim
Step 2: Use Vim in VS Code
Install Vim extension for VS Code to learn basics
Step 3: Transition to Neovim
Gradually adjust to using full Neovim in terminal
Step 4: Customize Neovim
Configure and use Neovim for enhanced productivity
Step 5: Continuous Learning
Keep learning and adapting Vim concepts for efficient workflow
Insights
Switching to Neovim from VS Code initially reduces productivity
the problem with switching to neovim or Vim in general is that it destroys your productivity it feels like being in primary school again and learning how to type.
Persistence leads to greater efficiency with Neovim
you feel like a wizard and you only sometimes feel like smashing your keyboard when you try to update some plugin and your editor is completely broken so the problem is it’s hard you’re going to code much more slowly for a while
Using Vim concepts in VS Code as a transition step is beneficial
you can start with just the basics by installing the Vim extension for vs code so this will allow you in a more familiar environment to start putting those basic Vim Concepts you learned from those videos into practice.
Custom Neovim configurations enhance productivity
getting something working with neovim probably isn’t going to be good enough because things will break if you understand the underlying Concepts at least somewhat you’ll be able to dig yourself out of holes much more effectively