When I look at an editor, I care about how much maintenance the configuration needs as well as how much I can customise it. Neovim gives you room to build your own setup: shortcuts, file search and the way it works with the terminal.
A plugin change can also leave you fixing the setup in the middle of something else. That's fine on a day when you feel like tinkering. Less so when you just want to open the project and work.
VS Code has more ready to use. Installing the extension a project needs and moving on can be easier. The tradeoff is a busier interface and higher resource use.
I find it more useful to think about the task. Editing a small file in the terminal and debugging an application aren't the same job. Choosing one editor doesn't have to mean giving up the other entirely.
Vim motions are a separate preference too. You can take some of those habits with you when you change editors.
Thinking through the same task in both editors
Suppose I need to find the callers of a function and change one of its parameters. Opening the file is only the start. I need references, type errors after the change, and perhaps a debugger to see how the application behaves.
In Neovim, that means having the language server and relevant shortcuts configured. A language server supplies information for completion, definitions and diagnostics. Neovim can use that information, with the setup depending on the plugins you choose.
VS Code needs the appropriate language support or extensions too. What I look at is how much of this workflow is ready for the project. If I keep leaving the editor to find references, rename symbols or debug, the setup isn't finished for what I need.
Vim motions are a separate habit. I mean commands like w to move to the next word in normal mode, or ciw to replace the word under the cursor. Liking those commands doesn't require moving the whole development environment into Neovim.