I have worked with MSVC a lot so that might tint my experience but I don’t get what’s so good with vs code. It kind of sucks in a classic windows way, many options for the same thing and often it just doesn’t work. Tried to set it up on linux with godot & c# (🥴) impossible to debug and autocomplete was like every library on earth, except godot ofc. What a pain in the butt.
Yeah, to be honest, I’ve given up on that one. “Language Server Protocol” is a classic case of Microsoft naming things.
The two differentiating words are “language” and “server”. It does not specify what kind of language is being served or what it even means to serve a language. And “server” is entirely redundant with it being a protocol. Not to mention, that “server” is the most overused word in IT and therefore virtually meaningless.
For all we know, it could be a protocol for butlers carrying French dictionaries.
So yeah, I use the acronym as its name, because it is similarly meaningful while being actually recognizable. And when I need to specify whether I’m talking about the “protocol named Language Server Protocol” or a “Language Server Protocol server” or even a “Language Server Protocol client”, I will just slap that behind the acronym and be done with it.
No one is going to take IntelliJ from me. Tab completion master race!
Lots of simpler editors gained tab completion support over the last few years, thanks to the LSP protocol. I have it in Kate, for example.
I dream of an alternate reality where everyone started using Kate instead of VSCode.
I have worked with MSVC a lot so that might tint my experience but I don’t get what’s so good with vs code. It kind of sucks in a classic windows way, many options for the same thing and often it just doesn’t work. Tried to set it up on linux with godot & c# (🥴) impossible to debug and autocomplete was like every library on earth, except godot ofc. What a pain in the butt.
The P in LSP, already stands for protocol :)) “Language Server Protocol”
Yeah, to be honest, I’ve given up on that one. “Language Server Protocol” is a classic case of Microsoft naming things.
The two differentiating words are “language” and “server”. It does not specify what kind of language is being served or what it even means to serve a language. And “server” is entirely redundant with it being a protocol. Not to mention, that “server” is the most overused word in IT and therefore virtually meaningless.
For all we know, it could be a protocol for butlers carrying French dictionaries.
So yeah, I use the acronym as its name, because it is similarly meaningful while being actually recognizable. And when I need to specify whether I’m talking about the “protocol named Language Server Protocol” or a “Language Server Protocol server” or even a “Language Server Protocol client”, I will just slap that behind the acronym and be done with it.
🫠