Neovim plugin authors forget one simple rule - plugins are supposed to plug in. Instead they write libraries.
I’ve been forking plugins I’m unwilling to get rid of and rewriting them to not require setup. It eliminates a lot of config complexity.
What worries me is that the same people that contribute to this mess are getting more and more involved with neovim core development. require.enable({ enabled = true}) is a recognizable [anti]pattern.
Sexual attractiveness also doesn’t mean sexual drive. One doesn’t need to be gay to understand that a man is sexually attractive in the way they find compelling. A desire to look good is all it takes.
I’m working with a legacy codebase for the last few months, where a simple PR often ends up crossing a 1000 lines count due to testing and commenting, and I can’t stop apologizing for those.
Yet there are people out there bragging about 10x changesets.
It would be perfect as a CLI and LSP combo.