There are several different LSP implementations of Elixir, each with their own pros and cons. Last year they all agreed to collaborate on an LSP; is this going to be the result of that?
The architecture is remarkable. The lengths they’ve gone to for language version compatibility, and protecting app namespaces is especially impressive.
It has both a justfile and a makefile at the root, even. Most of us seem to want to use it to throw make away entirely.
That said, I consider `just` very language-agnostic and useful because of that, and I consider mix pretty bad at any workflow needs that isn't directly concerned with BEAM.
zamalek · 53m ago
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.
0x457 · 11m ago
IMO 'just' replaces make where make shouldn't be used - generic task runner.
MangoToupe · 1h ago
I think it's hard for me to name better software than make. TeX, maybe? that seems like an insanely high bar to clear.
keeganpoppen · 2h ago
i'm a pretty big fan of just, personally, but do not consider that to be the world's most well-considered position by any means...
https://elixir-lang.org/blog/2024/08/15/welcome-elixir-langu...
https://github.com/elixir-lang/expert/blob/main/pages/archit...
That said, I consider `just` very language-agnostic and useful because of that, and I consider mix pretty bad at any workflow needs that isn't directly concerned with BEAM.