You and I must have different definitions of "0 configuring". There is no "one" LSP client, so every time I want to spend time training my vim muscle I have to research basically which one [is the best/has the most problems or users], whether the language server works well with it, figure out which plugin manager I should be using, write down and remember the shortcuts to invoke my plugin manager, set up key bindings, set some more configuration flags, then maybe have something working by the end of the day.

After all that, yea I'm more productive but I think the large barrier of entry to CLI editors is what keeps people using IDEs and their Electron cousins.

Installing an LSP is already configuring, so it's not 0.

If that's true, I'd really like to try that. I've never heard of ALE, so thanks for that.

Still, the fact is that you have to know what to install. It's not like the NeoVim manpage mentions any LSP clients. So it requires a lot of tinkering, reading and participating in the community to figure out how to do stuff. That's exactly opposite of 0-configuring.

If NeoVim could bundle an LSP client with it, and have a config key to enable it, that'd be dope.

Neovim does bundle an LSP client.You can launch and attach with ~6 LoC. See `:help lsp`

https://paste.sr.ht/~mjlbach/1a1df5cd61627e87ea4c4355a0473bf...

I did not know about this. Thanks!

Of course :) Lspconfig adds an autocommand that does this for you when it detects the filetype, and includes the start commands (that's it, all the other functionality is in core.