3 ms·
How are you finding the performance of LSP? I dropped Emacs for NeoVim because Emacs would frequently lockup for a second or more due to LSP. NeoVim doesn't ha
by weavie 5y ago
How are you finding the performance of LSP?
I dropped Emacs for NeoVim because Emacs would frequently lockup for a second or more due to LSP. NeoVim doesn't have this problem.
I would love to return to Emacs someday.
- cle 5y agoI don't experience any performance problems with lsp-mode, it is very snappy and never gets in my way of going from thought->code. In particular, Go's LSP support is excellent and very fast. I've found these days that the LSP perf is up to the LSP implementation, not Emacs.
- weavie 5y agoInteresting. I'm using Rust on a fairly large project. I guess that takes a hefty chunk of processor time to work with, which causes Emacs to lock up and NeoVim not to..
- na85 5y agoI only use some of the more mature ecosystems (C#, Microsoft's Python language server, golang, etc) but I've always found the performance to be good.
- natrys 5y agoFrom 27.1 Emacs could be configured to use a native library (jansson) for json parsing, it helped LSP a lot. And now there is a new native-comp feature, where you can AoT compile elisp bytecode to native code with libgccjit, which improves Emacs performance in general. Anecdotally, a few months ago I wrote some Flutter on a potato laptop, NeoVim native LSP client + nvim-compe was borderline unusable. The vim-lsc somehow fared much better - albeit still choppy - even though it's written in vimscript. Emacs + eglot is the only combination that was smooth.