Here's the thing, though. I don't use Vim as an IDE. I use it on live servers to change configs / scripts / app code (don't tell anyone) quickly and efficiently. I don't think "extra doodads" would help with that, and I'm not sure I'd want to manage those dependencies on my platform anyway.
If I'm actually developing something that's part of a greater whole, then I'm using a fully fledged IDE like PyCharm (but with the VIM emulator plugged in for when I need it, of course ;-D).
Likewise, no shade at Emacs, though. Several of my favorite colleagues use it!
Contrary to what many might expect, Emacs tools are quite good for performing sysadmin tasks:
* TRAMP for remote editing. It's more powerful than Vim's netrw remote editing capabilites and can handle root-owned files on remote servers. It's so extensible there's even a package that allows you to edit files inside Docker containers running on remote servers.
* Dired. It's the best text-based file manager out there IMHO, and it integrates very nicely with TRAMP.
* Org mode. It can be used like Jupyter notebook, but is far more powerful. You can write each code block in any language you choose, pass data between them, and make each of them run on different servers. This is very useful for sysadmin tasks especially in professional environments because it allows you to document each step in a reproducible manner as you're executing it. You can then just share the org document for your cowokers to review.
I personally use Vim for coding and Emacs for non-trivial sysadmin tasks.
If I'm actually developing something that's part of a greater whole, then I'm using a fully fledged IDE like PyCharm (but with the VIM emulator plugged in for when I need it, of course ;-D).
Likewise, no shade at Emacs, though. Several of my favorite colleagues use it!