12 ms·
Not the person you are replying to, but the JSON performance of Emacs was a well-known thorn in the side for using LSP. Further details... ... from the same s
by shepmaster 3y ago
Not the person you are replying to, but the JSON performance of Emacs was a well-known thorn in the side for using LSP.
Further details...
... from the same source as the top post: https://www.masteringemacs.org/article/speed-up-emacs-libjansson-native-elisp-compilation https://www.masteringemacs.org/article/speed-up-emacs-libjan...
... from lsp-mode: https://emacs-lsp.github.io/lsp-mode/page/performance/#json-native-serializationdeserialization https://emacs-lsp.github.io/lsp-mode/page/performance/#json-...
- oblio 3y agoAh, ok, I get what you mean, but those are not inherent JSON issues. After all, VS Code & co use the exact same protocol in a speedy fashion. It's Emacs needing to be configured to use faster JSON libraries. The original comment was complaining about JSON as a format itself, and my argument is that unless you need super high performance, JSON is more than enough. And it's not like LSP is passing around GB of data every second, let's be real here :-)