4 ms·
> LSP had been a game changer, for Emacs and all other editors Not for me. I've tried to use LSP for Chromium's code base(~40k files) and it was miserable. It
by slezyr 6y ago
> LSP had been a game changer, for Emacs and all other editors
Not for me. I've tried to use LSP for Chromium's code base(~40k files) and it was miserable. It took 8-10 hours to index it and each time the LSP server started it used 10GB of RAM to work.
Comparing it QtCreator's Code Model (the old one which everyone hates, not clang based) takes 2 Min to start from zero without blocking the GUI.
- ddavis 6y agoWhat language server did you use? These days both ccls and clangd should be able to handle Chromium.
- slezyr 6y agoccls, they can handle Chromium, but after 8-10 hours of indexing and then it uses 10GB of RAM when you launch the editor.
- NateEag 6y agoI've used language servers in large, old codebases that took a while to parse, and they never blocked the GUI for me. I only got intelligence on as much of the project as it had finished parsing at a given point in time, obviously, but I wasn't stuck waiting for it to finish before I could work. This was using php-language-server and lsp-mode for Emacs.