4 ms·
Rust's IDE story is starting the year off with a bang. :) It's taken me until now to realize that the protocol is semi-standardized: https://github.com/Microsof
by kibwen 10y ago
Rust's IDE story is starting the year off with a bang. :) It's taken me until now to realize that the protocol is semi-standardized: https://github.com/Microsoft/language-server-protocol https://github.com/Microsoft/language-server-protocol . Are Rust and Typescript the only two languages with implementations of this protocol so far? (EDIT: nevermind, found http://langserver.org/ http://langserver.org/ , which implies there are quite a lot of these.)
I'm also fascinated to hear that it's using both Racer and rustc to provide autocomplete. Is there any long-term plan to provide "quick and dirty" info from the compiler itself rather than from Racer? EDIT 2: Ah, the final paragraph addresses this. That's what I get for commenting before I'm done reading. :P
- bluejekyll 10y agoEclipse is working on one for Java I think: https://projects.eclipse.org/proposals/jdt-language-server https://projects.eclipse.org/proposals/jdt-language-server
- schmichael 10y agoThe wiki has a list: https://github.com/Microsoft/language-server-protocol/wiki/Protocol-Implementations https://github.com/Microsoft/language-server-protocol/wiki/P...
- spott 10y agoI wonder why C++ isn't on this list.
- steveklabnik 10y agoIt's the second entry in the table here. Links to https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools https://marketplace.visualstudio.com/items?itemName=ms-vscod...
- deleted 10y ago[deleted]
- 404-universe 10y agoAre there any implementations of the language server protocol for vim or emacs?
- steveklabnik 10y agohttps://github.com/tjdevries/nvim-langserver-shim https://github.com/tjdevries/nvim-langserver-shim https://github.com/sourcegraph/emacs-lsp https://github.com/sourcegraph/emacs-lsp (linked from the langserver page)
- int_19h 10y agoAs someone who had worked on language support in IDEs for the past 5 years, it's really great that we have finally arrived to the point of getting common protocols. IDEs have historically been very self-contained, each with its own ecosystem, resulting in a lot of unnecessary duplication of effort. Now, at last, we can do neat things that are immediately usable across the entire language ecosystem at once. Better yet, we can have language designers implement support themselves, ideally using the same code that powers their compiler. Historically, tooling support has been the single biggest stumbling block for new languages, no matter how promising. This should significantly reduce the barrier to entry for that, and make new languages more viable as a result. The fact that it can also be used to "light up" hardcore editors like Vim and Emacs is also a nice bonus!
- josteink 10y ago> it's really great that we have finally arrived to the point of getting common protocol This. Common protocols is what has helped us independently, incrementally and exponentially make the internet more useful. If we can (finally?) get this lesson learned down to the application level, computing may finally start advancing conceptually once again. Right now we've been in a rinse/repeat standstill iteration for god knows how many years. But I guess everyone is too busy trying to get rich building the next big closed service to consider fundamental issues like that...
- flukus 10y ago