Langserver.org – A community-driven source for Language Server implementations
1–10 of 27 posts
Re: Langserver.org – A community-driven source for Language Server implementations
#2THe SourceGraph server for Go is deprecated in favor of 'gopls'. This is documented on the sourcegraph github page.
Re: Langserver.org – A community-driven source for Language Server implementations
#3Quick piece of feedback: the big table with all the languages could use a color other than red (gray?) for "Not Applicable". For example, I assume that's the reason JSON is missing "Jump to def", "Find references", etc.
Re: Langserver.org – A community-driven source for Language Server implementations
#4A thread from 2017: https://news.ycombinator.com/item?id=15711604
Re: Langserver.org – A community-driven source for Language Server implementations
#5I 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.
Re: Langserver.org – A community-driven source for Language Server implementations
#6Where can I found a feature comparison of state of the art LSPs vs intellij idea features?
What can one do that the other cannot?
Re: Langserver.org – A community-driven source for Language Server implementations
#7It seems that Language Server Index Format (LSIF) https://code.visualstudio.com/blogs/2019/02/19/lsif is the successor to the Language Server Protocol (LSP). LSIF supports code navigation without having all source code files available on a local disk like LSP requires.
Re: Langserver.org – A community-driven source for Language Server implementations
#8It seems that Language Server Index Format (LSIF) https://code.visualstudio.com/blogs/2019/02/19/lsif is the successor to the Language Server Protocol (LSP). LSIF supports code navigation without having all source code files available on a local disk like LSP requires.
Good to know thank you
Re: Langserver.org – A community-driven source for Language Server implementations
#9I 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.
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.
Re: Langserver.org – A community-driven source for Language Server implementations
#10THe SourceGraph server for Go is deprecated in favor of 'gopls'. This is documented on the sourcegraph github page.
It's interesting that langserver.org is actually run by SourceGraph and it's still out of date.