For those of you who are just starting to use vim, these are two distinct processes:
1. Use vim
2. Setting up vim
Without putting focus on 1, it will be harder to learn 2.
I started vim-bootstrap in 2014 when many people were forcing my dotvim repository. I found this absurd as it was my personal vim repository, given this behavior of people I decided to understand why they were forking, after some people (exchanging emails with them) I understood that they were using my vim files as a base for their vim files.
The vim-bootstrap should not be used for "the rest of your life", but to be the "bootstrap" for those who are starting to use vim, after learning that it is time to fly solo and create their own vimfiles.
@eugeny_schibrikov we have a working initiative to make transparent which plugins are part of the package for each language and give you the possibility to disable the ones you don't like.
we need support to develop new features, if you are interested in contributing follow the issue: https://github.com/editor-bootst...
Vim Bootstrap