The byte code compiler uses gccjit to compile elisp to elf files. That, in conjunction with the use of libjansson for json handling, makes emacs substantially, noticeably faster for lsp (language server protocol, which most editors at least have support for now).
If you haven't looked at lsp yet either, I'd highly recommend it. It provides a common set of language server apis so you can have a unified completion experience between languages. I can remember all the unpleasant tricks to getting jedi mode for python, meghanada for Java, and having to memorize two totally separate apis. This is so much nicer.
The byte code compiler uses gccjit to compile elisp to elf files. That, in conjunction with the use of libjansson for json handling, makes emacs substantially, noticeably faster for lsp (language server protocol, which most editors at least have support for now).
If you haven't looked at lsp yet either, I'd highly recommend it. It provides a common set of language server apis so you can have a unified completion experience between languages. I can remember all the unpleasant tricks to getting jedi mode for python, meghanada for Java, and having to memorize two totally separate apis. This is so much nicer.