[prince781]

> This feels like a move away from plugins and into monolith territory, which feels like a big step.

I don't consider LSP to be a monolith. You still have the decentralization of language server development. Rather, LSP is just a standardization of what we have come to expect from editors interacting with plugins. And because the standard is modular in its features, the barrier to entry for new language servers and editors remains low.

As a standard, I don't think LSP encourages monopolization the way that the web does for browsers.

[gen220]

To be clear, I was saying that integrating LSP into neovim makes neovim more monolith-y than it was prior, not that LSP was a monolith! :)

[prince781]

Ah, I misread your comment. My apologies.

Yeah, perhaps this does make neovim more a monolith, as there are already great plugins like coc.nvim that can be used. However, I believe the expectations of a modern text editor have been raised sufficiently in the last few years that we now expect to have code intelligence baked in, just like we came to expect baked-in syntax highlighting decades ago over editors that lacked it back then.

[kzrdude]

Well, VSCode has a controlling position in the LSP ecosystem, so we literally have microsoft looming over it.