I use (N)VIM. I only use small amount of plugins, which are mostly plugins to enhance syntax highlighting. I write code a lot so I know the linting rules from the top of my head. More often than not the linter won't complain, so I don't really need linting on the fly. For type checking, same thing, I most likely have to look at the code anyways.
I run the linter, type checker and tests in a separate terminal tab (with split views). So before I commit I quickly switch to that terminal tab, see whether everything is ok and I am good to go.
My VIM is blazing fast and barely uses any resources. It launches nearly instantly and rarely gets in my way.
Quite efficient for me personally. I am not saying it would work for you, I am merely showing the way I use it. It's a bit of a different approach. You're trying to use VIM as an IDE. For me, my entire terminal is the IDE, of which VIM is a small part.
I run the linter, type checker and tests in a separate terminal tab (with split views). So before I commit I quickly switch to that terminal tab, see whether everything is ok and I am good to go.
My VIM is blazing fast and barely uses any resources. It launches nearly instantly and rarely gets in my way.
Quite efficient for me personally. I am not saying it would work for you, I am merely showing the way I use it. It's a bit of a different approach. You're trying to use VIM as an IDE. For me, my entire terminal is the IDE, of which VIM is a small part.