4 ms·
Interestingly, as an emacs user, I am really rooting for the success of VSCode. The existence of the Language Server Protocol means that I have a horse in this
by runarberg 6y ago
Interestingly, as an emacs user, I am really rooting for the success of VSCode. The existence of the Language Server Protocol means that I have a horse in this race. Emacs users that use the same language server as VSCode users directly benefit from this relationship. So even though VSCode is competing with Emacs for market share, it is very much collaborating with Emacs (and other text editors that use LSP) in making language features comprehensive for everybody.
- reidrac 6y agoI feel the same. I couldn't do Scala with vim if it wasn't for LSP and Metals. (and I'm aware that I still have less features than if I was using a full featured IDE, but I'm still very productive and also happy)
- loosetypes 6y agoAny resources you could recommend for getting started re LSP with emacs?
- runarberg 6y agoI personally started with lsp-mode[1] and just went from there. 1: https://emacs-lsp.github.io/lsp-mode/ https://emacs-lsp.github.io/lsp-mode/
- owl57 6y agoIt's more complicated. Microsoft waits until everybody adopts LSP for, say, Python, and then slowly moves to a proprietary language server, explicitly forbidding its use outside VSCode: https://news.ycombinator.com/item?id=25719338 https://news.ycombinator.com/item?id=25719338