3 ms·
My problems are mostly with the language servers. I've always found them to be slower, consume more resources, and provide worse results compared to the equival
by robhlt 5mo ago
My problems are mostly with the language servers. I've always found them to be slower, consume more resources, and provide worse results compared to the equivalent JetBrains IDE. I've tried Python, Rust, and Go within the last few months and found this is still the case. Go is the worst of them, on larger repos gopls will easily consume 3-4x more memory than GoLand with far worse responsiveness on completions.
- ElectricalUnion 5mo agoJetbrains IDE, sure, they take their sweet time indexing your project, but once per start. The Java LSP is a egregious "thing" that takes 10 to 30s to read your whole project for the n-th time while eating 40GiB of RAM in the process. On a loop, EVERY time you view a new file. Where is my goddam lsif/scip support?
- mike_hearn 5mo agoYou shouldn't be seeing indexing once per start. The indexes are stored to disk. You might see the IDE scan files to figure out if anything changed whilst the IDE was stopped.
- ElectricalUnion 4mo agoHow did you manage to get the Java LSP to do that? Mine just insist on re-parsing the entire codebase every time I view a file.
- mike_hearn 4mo agoAh sorry, I've never used that. I was talking about IntelliJ and related IDEs.