Live data from Hacker News

Expert: LSP for Elixir

github.com

21–30 of 47 posts

Re: Expert: LSP for Elixir

#21

I’ve been switching between different LSP implementations for Elixir—ElixirLS, Lexical, next-ls—and have been following Expert for a while. Really looking forward to trying it out! That said, the only thing that feels a bit off to me is the name “Expert.” It comes across slightly arrogant or presumptuous—like it’s implying it’s the only “expert” in the room. Maybe something more neutral would’ve been better? Still, e…

It's not an AI tool. It's an LSP. It is the expert in the room, because it's not a random word generator, not smart, it just follows the rules that the language has.

Re: Expert: LSP for Elixir

#24
post #11
post #8

Earlier quoted context omitted.

It's not technically a make replacement (make does do things like incremental build management etc.), but it just goes to show how bad the DX of make is.

IMO 'just' replaces make where make shouldn't be used - generic task runner.

Correct. Make should be used with the filesystem, minimising PHONY.

Re: Expert: LSP for Elixir

#26

I’ve been switching between different LSP implementations for Elixir—ElixirLS, Lexical, next-ls—and have been following Expert for a while. Really looking forward to trying it out! That said, the only thing that feels a bit off to me is the name “Expert.” It comes across slightly arrogant or presumptuous—like it’s implying it’s the only “expert” in the room. Maybe something more neutral would’ve been better? Still, e…

I found the name to be perfect. Just a little fun. It also goes with the ex-prefix you see in libs sometimes.

Re: Expert: LSP for Elixir

#27
post #5

The architecture is remarkable. The lengths they’ve gone to for language version compatibility, and protecting app namespaces is especially impressive. https://github.com/elixir-lang/expert/blob/main/pages/archit...

What are namespaces in Elixir?

Namespaces aren't so much a concept in Elixir, but this refers to the names used for things like modules. Expert will rewrite the code of its "engine" so that the engine's code and dependencies and those of the application it is embedded into don't overlap.

Re: Expert: LSP for Elixir

#29

I’ve been switching between different LSP implementations for Elixir—ElixirLS, Lexical, next-ls—and have been following Expert for a while. Really looking forward to trying it out! That said, the only thing that feels a bit off to me is the name “Expert.” It comes across slightly arrogant or presumptuous—like it’s implying it’s the only “expert” in the room. Maybe something more neutral would’ve been better? Still, e…

How did you find out about it in the first place? I remember seeing the Elixir blog post announcing the LSP project ages ago and then nothing since then.

Re: Expert: LSP for Elixir

#30

I’ve been switching between different LSP implementations for Elixir—ElixirLS, Lexical, next-ls—and have been following Expert for a while. Really looking forward to trying it out! That said, the only thing that feels a bit off to me is the name “Expert.” It comes across slightly arrogant or presumptuous—like it’s implying it’s the only “expert” in the room. Maybe something more neutral would’ve been better? Still, e…

How about "Fairly Knowledgeable, Always Humbly Ready to Learn from Others"? FKAHRLO for short.

Nailed it
Post reply on HN