Yeah that's got it reversed. Vim is overkill for editing configuration files. You see people use vim for configuration files because it's there and they already

Yeah that's got it reversed. Vim is overkill for editing configuration files. You see people use vim for configuration files because it's there and they already know how to use it. If you really want to ease into it then simply enable the (neo) vim plugin in vscode, it's pretty good. You'll miss some big features but you'll have all the bread and butter features. Only risk is that you'll get used to some vscode features as well.