The existence of multiple LSP clients demonstrates the success of LSP and is a strength, not a weakness as the author suggests. Often, it's because LSP clients

The existence of multiple LSP clients demonstrates the success of LSP and is a strength, not a weakness as the author suggests. Often, it's because LSP clients have differences not in interacting with the LSP Server, but in how that is surfaced to the user. Some LSP clients are written in different languages, and that can make some implementations faster than others. This is why LSP is a success. It allows for clients to be written in many ways but for all of them to do the most basic thing they need to (go to def, rename, refactor, search symbols etc). Multiple LSP clients is a success and offers users more choice about how they want to interact with their code. Do I want a search for symbols to open in a new window, to replace the current buffer, in a searchable list etc.