Hacker News Reader

Comment by jpe90 | Hacker News Reader

I'm also on an AMD 3700X, 32G of RAM, with Emacs native compilation branch. I'm totally unaware of elisp vs native JSON parsing though, I was just using stock Eglot that came bundled with Emacs.

View on HN

It's more a question of where you got your Emacs. Native compilation, native JSON parsing, and a bunch of other things are configure-time options.

Oh I see, I build from source but I’ve been using the same configure options forever (just native comp and rename the ctags binary). I’ll look them over again.

Check that you have `libjansson-dev` installed, or whatever is the equivalent on your system.

Looks like I’ve got that on my machine, and I built Emacs —with-json this time. Performance is still better but it’s still stuttery.

I guess it’s related to either the json parsing happening on the main thread and/or the LSP servers using company-capf which I think is a synchronous backend?

It seems like coc.nvim, lsp bridge, kak-lsp, and other editor solution’s i’ve come across all opt to use sidecar processes that manage lsp. Perhaps Elisp isn’t the right tool for that backend processing.

This can be spun off into another thread. I haven't tried it yet but the feedback has been excellent.

https://reddit.com/r/emacs/comments/ymrkyn/async_nonblocking...

Oh what a great idea! I hope this can get mainlined someday(perhaps behind a config option) since Eglot should benefit from that approach as well!

Reply on news.ycombinator.com