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.
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.
Honestly just memorize the fundamental ones and google everything else you need on the fly. You’ll naturally memorize the ones you use often.
I’ve used VIM for nearly 5 years and the only keybinds I have memorized are ‘a’ (append right here) ‘A’ (append to end of line) ‘i’ (insert right here) and I use the arrows to navigate instead of the letters. The only incantation I have memorized is %s/text to replace/text to replace with/g (find and replace through entire file. Remove the /g to find and replace only the next instance).
Once you have those, you can basically do anything that you’re capable of in a normal editor. If you need to do something beyond that, search “how to x in vim” and click the first stack overflow link that comes up, hasn’t failed me yet
It’s very hard to break up a flow to have to google. :D I found a cheatsheet that I will keep open on another monitor, that should help. I reckon going through the Vim Tutor every day should help me get the basics down quickly.
Thanks for the tips, my hope to switch away from IDEs is higher than ever!
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.
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.
🫠
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.
Sub renewal is coming up in July. I’m seriously wondering whether I can get these vim bindings down before then.
You can keep using the current version without renewing your license, so there is no rush
Wow great tip, thanks!!!
Honestly just memorize the fundamental ones and google everything else you need on the fly. You’ll naturally memorize the ones you use often.
I’ve used VIM for nearly 5 years and the only keybinds I have memorized are ‘a’ (append right here) ‘A’ (append to end of line) ‘i’ (insert right here) and I use the arrows to navigate instead of the letters. The only incantation I have memorized is %s/text to replace/text to replace with/g (find and replace through entire file. Remove the /g to find and replace only the next instance).
Once you have those, you can basically do anything that you’re capable of in a normal editor. If you need to do something beyond that, search “how to x in vim” and click the first stack overflow link that comes up, hasn’t failed me yet
If you want to start using Vim the way i was intended to be used. You should really learn touch typing. Also, text objects are a pretty big deal IMHO.
It’s very hard to break up a flow to have to google. :D I found a cheatsheet that I will keep open on another monitor, that should help. I reckon going through the Vim Tutor every day should help me get the basics down quickly.
Thanks for the tips, my hope to switch away from IDEs is higher than ever!