Why LSP?
LSP (language server protocol) is fairly popular today. There's a standard explanation of why that is the case. You probably have seen this picture before:
LSP ( language server protocol ) is fairly popular today. There’s a standard explanation of why that is the case. You probably have seen this picture before: I believe that this standard explanation of LSP popularity is wrong. In this post, I suggest an alternative picture. Standard Explanation The explanation goes like this: There are M editors and N languages. If you want to support a particular language in a particular editor, you need to write a dedicated plugin for that. That means M * N work, as the picture on the left vividly demonstrates. What LSP does is cutting that to M + N , by pro
related reading
- Understanding the Language Server Protocol | by Malintha Ranasinghe | Mediummedium.com
- A half-hour to learn Rustfasterthanli.me
- You Can Choose Tools That Make You Happyborretti.me
- What are Domain-Specific Languages (DSL) | MPS by JetBrainsjetbrains.com
- HiPhish's Workshophiphish.github.io
- Async Rust Is A Bad Languagebitbashing.io
- Why Rust - Rust for C-Programmersrust-for-c-programmers.com
- The language strangeness budgetsteveklabnik.com
- Weird Languagespaulgraham.com
- The Alternative Implementation Problempointersgonewild.com
- The Future of Programming: Copilots vs. Agents (Part I)eastwind.substack.com
- Rethinking Visual Programming with Go · divan's blogdivan.dev