Imagine your editor can ask an expert questions about the codebase and help you navigate it that way. Then the editor doesn’t need to know much about each language – all the cool analysis is handled by the language-specific program.
That language expert program is the “language server.” It’s called a server because the editor can throw requests at it exactly the same way you’d ask a backend server for information.
In general, you shouldn’t think of a “server” as something that *has* to run remotely. You have *plenty* of computing power on your workstation to run local servers, and that’s typically how server development is done.
Latest Answers