3 ms·

I have to say that list has gotten waaay longer since last time I saw it. LSP really has been a massive success, and despite being made by MS, has been one of

I have to say that list has gotten waaay longer since last time I saw it. LSP really has been a massive success, and despite being made by MS, has been one of the main reasons I’ve been able to keep using Emacs and not migrated to other more IDE-like editors. MS deserves som serious credit here for being one of the few players willing to think in protocols these days. Protocols vs products makes a big difference.

_bxg1 7y ago
It's truly one of those I-can't-believe-nobody-thought-of-this-before ideas. And beyond the obvious benefits to developers' experience, it's also a huge boon to smaller language projects. If you build a new, open language and don't have the backing of a huge company, you definitely don't have the resources to integrate it directly with every editor someone might want to write it in. But you might be able to put together a single language-server.
- mikewhy 7y ago
  There was (and still is) YouCompleteMe for Vim, which is the idea of a code-completion server with editor plugins, so it's definitely a thing people had thought of. Microsoft really took the ball and ran with it, and I'm very grateful for that.
- charlieflowers 7y ago
  I think Slime for Emacs was the first to think of it, a looong time ago (at least it was the first place I saw the idea in action). Edit to clarify -- Slime was never meant for general use across many languages. But Slime had the "smarts" in a separate process and communicated with the editor via the network.
- LessDmesg 7y ago
  I know I'm making an LSP implementation for my personal language. A total must-have.
int_19h 7y ago
While we're at it, there's a similar, albeit lower-key, effort for debuggers: https://microsoft.github.io/debug-adapter-protocol/specification https://microsoft.github.io/debug-adapter-protocol/specifica... One example of use outside of Microsoft products: https://github.com/puremourning/vimspector https://github.com/puremourning/vimspector

_bxg1 7y ago

It's truly one of those I-can't-believe-nobody-thought-of-this-before ideas. And beyond the obvious benefits to developers' experience, it's also a huge boon to smaller language projects. If you build a new, open language and don't have the backing of a huge company, you definitely don't have the resources to integrate it directly with every editor someone might want to write it in. But you might be able to put together a single language-server.

mikewhy 7y ago
There was (and still is) YouCompleteMe for Vim, which is the idea of a code-completion server with editor plugins, so it's definitely a thing people had thought of. Microsoft really took the ball and ran with it, and I'm very grateful for that.
charlieflowers 7y ago
I think Slime for Emacs was the first to think of it, a looong time ago (at least it was the first place I saw the idea in action). Edit to clarify -- Slime was never meant for general use across many languages. But Slime had the "smarts" in a separate process and communicated with the editor via the network.
LessDmesg 7y ago
I know I'm making an LSP implementation for my personal language. A total must-have.

int_19h 7y ago

While we're at it, there's a similar, albeit lower-key, effort for debuggers: https://microsoft.github.io/debug-adapter-protocol/specification https://microsoft.github.io/debug-adapter-protocol/specifica... One example of use outside of Microsoft products: https://github.com/puremourning/vimspector https://github.com/puremourning/vimspector