Post
This is a huge milestone for the new #ElixirLang LSP.
At Jump, we’ve had Paweł Świątkowski (katafrakt on the internet) working full time getting Expert dialed in for our large codebase. The stability and reliability are now hands down the best Elixir LSP experience I’ve had, and we’re not done yet.
Congrats to all the contributors! 🥂
@tylerayoung After Expert first came into existence, I had so much trouble with it that I made my own LSP. Recently I've given it another try and it's much improved, and I'm using it full time.
@j3rn out of curiosity, why make your own LSP instead of reporting issues and helping improve Expert?
@dorgan I looked into contributing to Expert, but its architecture was very different from what I had in mind and, in my opinion, was overcomplicated.
I got pretty decent mileage out of just reading files and parsing symbol info out of ASTs, though it has the existential problem of assuming that a `defmodule` call defines a module and a `def` call defines a function, which is not true in all instances (can be overridden).
@j3rn And what were the issues you had with Expert? Because we can't fix what we're not aware of if people don't post issues and sorry if I sound rude but the point of Expert is to be done with several LSP implementations. What you just mentioned is one of the many reasons why Expert has the architecture it has.
@dorgan The issue I was having with Expert several months ago was that it would spike my CPU to 100% and gobble RAM until my laptop had to be force-restarted.
Happily this seems to no longer be happening.
