New comment by mitinarseny on void-packages repository

https://github.com/void-linux/void-packages/pull/37795#issuecomment-1177317189

Comment:
> Does anything bad happen when the plugin is loaded by default? 

It just should not be loaded unless the user explicitly say that... Imagine installing a bunch of other command-line utilities which has [neo]vim plugin support. But I just want to use them as command-line utilities and not inside neovim. Even if this plugin does not create any mappings, I don't want it to be sourced by default becasue:
* it increases startup time of neovim
* it can contain deprecated or even removed functionality which would cause an error while loading neovim

You can think of it as the same as if packages with `sv` services would be shipped with already symlinked service directories to `/var/service` with `down` file present. I don't want this functionality to be enabled by default

> But it'd be a breaking change for some users and probably confusing if no other distro does this

With this approach we can end up using systemd and other ugly things from distos where end users do not have an opportunity to decide what they want and what they do not.