[cpow85]

Right, The point was about configuration. I had a configuration that worked for a couple years, then I start a new job and the config breaks on the first 50+ line TSX file. Now I have to go and find the culprit, find a replacement plugin (in this case, yajs JS parser was slowing things down). and before I knew it, I was re-configuring everything again. I was more criticizing the ecosystem of plugins and how brittle some may be.

[mmm_grayons]

That's definitely a huge issue. I've had the same experience of having to spend hours to a day getting my configuration set up for a new language. I think part of the problem is that there's no basic config for a language (as with other editors) from which users can tweak, mostly because anyone who tried to get vim users to standardize on any defaults other than those shipping with vim itself would be strung up and horse-whipped as a purveyor of bloat. Vim is a great editor and I love using it, but many community members have a "leet" attitude that discourages new users who need help.

It would be a whole lot easier if someone put together a set of basic configs for various languages that had language servers, completion, etc. and everyone referred new people to those. It's much easier to tweak and replace stuff than to assemble an entire config wholesale.

[daotoad]

I was using ALE for autocompletion and such, but having switched to COC, I find its support for TypeScript to be far superior.

This is relevant because COC is basically a system for talking to language servers.

https://github.com/neoclide/coc.nvim

[mmm_grayons]

Yep, I too have switched to it and pair it with CCLS for my C/C++ development. It works great after learning it and does significantly reduce the overhead needed for new languages. It's a little tricky to set up for new users, but it's nice that things have improved so much.