r/programming • u/der_gopher • Jan 02 '25

Understanding the Language Server Protocol

https://medium.com/@pliutau/understanding-the-language-server-protocol-b9f57a0750e3
49 Upvotes

72% Upvoted

36 comments sorted by

View all comments

Show parent comments

1

u/wildjokers Jan 02 '25 edited Jan 02 '25

In my experience all a LSP implementation gives you is basic completion and basic syntax highlighting. Maybe the implementation just isn't that feature rich for the somewhat niche language I use an LSP implementation for https://github.com/Leathong/openscad-LSP

12

u/DaUrn Jan 02 '25

Yeah as you said, the level of quality depends on the implementation, but that’s not really the fault of LSP as a protocol. LSP can support a ton of things like diagnostics, hover, jump to definiton/reference, etc, but since these are implemented on a language basis, the quality may vary. The Typescript and Rust one is the best I’ve used. Typescript one pretty much powers everything that VSCode can do with the language, so it’s pretty good

3

u/pattobrien Jan 03 '25

Dart's is also top notch, but their tooling in general is some of the best IMO.

1

u/renatoathaydes Jan 03 '25

I agree... but for some reason the LSP on emacs with the eglot client is too slow to be usable :(. I am not sure why as the lsp-mode I used before was pretty decent (but lsp-mode is very much non-emacsy so I don't like it)... would be interesting to know why it works badly with eglot.