21–27 of 27 posts
It 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.
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.
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 toget…
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.
Another thing I really like about LSP is that formatting and linting are built-in concepts. Using something like https://github.com/iamcco/diagnostic-languageserver you can bridge existing command-line tools that only support stdio into your editor of choice.
https://github.com/microsoft/language-server-protocol/issues...
Given this, I wonder what the future holds for JetBrains. They've made a good business out of providing standalone solutions for the more popular languages.
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.
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 toget…
Given this, I wonder what the future holds for JetBrains. They've made a good business out of providing standalone solutions for the more popular languages.
Additionally, they provide a uniform editing experience for a load of languages, which is one of the things I love the most. Where you’re writing go, python, java m, cpp or rust, the refactorings work similarly.
(I am kind of a fanboy)
It 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.
Maybe "successor" isn't the right word, as per the linked article: > The goal of the Language Server Index Format is to augment the LSP protocol