elixir-ls VS livebook

No. Not even close. But it's getting better.

There are currently two worth mentioning:

ElixirLSP: https://github.com/elixir-lsp/elixir-ls

Elixir tools: https://www.elixir-tools.dev/

ElixirLSP is the older project, and has been around for a while. It does a lot, but has had sporadic issues over the years. Things like the debugger are a dog to get working, and the server itself will occasionally run into issues where it just doesn't want to work. It's always sort of focused on a subset of language server features, so don't expect much in the way of inline corrections. But it's got the essentials, formatting, basic linting, type hinting, on demand documentation, and primitive reference navigation

Elixir tools is a new up and comer, written by Mitchell Hanberg. It's aiming to be a more complete lsp, and has plugins in its "ecosystem" for most editors. Features have been arriving rapidly, starting with things like inline corrections and far more reliable linting, and recently growing autocomplete. One of the main selling points is the elixir-tools backend is a self contained binary, so it can mostly work independent of system Elixir/Erlang version, which was a frequent tripping point for ElixirLSP

Personally I use both at the same time, but plan to move to tools only when it's got all the features I need

I decided I can live without elixir-ls when couching in return for having a usable editor. When the plugin ecosystem and documentation matures I can see myself switching to using Lapce for my primary editor.

Hi! I've compiled gdb from master and installed it. When I run gdb -i dap, I get JSON-RPC, so it looks like it's working, but I'm lost as to where to go from here. Does your change enable me to use a tool like https://github.com/elixir-lsp/elixir-ls with GDB now, right? How might I use them together? What would be required to then have GDB debugging over DAP from inside Emacs?

Elixir-ls provides Language Server Protocol support as well as VS Code Debug Protocol support which gives extra powers to VS Code, NeoVim, Emacs, and the like

https://github.com/elixir-lsp/elixir-ls

BUT, with the news that in the next Emacs version eglot (lsp client) is going to be in the core, I decide to modify alchemist in a different way, enhancing other capabilities and letting eglot do what he best does (which is the functionality of elixir-ls).

I think it's here: https://github.com/elixir-lsp/elixir-ls

elixir-ls powers the VSCode experience, and while it works decently, I've never really clicked with VSCode. In general, for other languages, I tend to use Jetbrain's Products. I would love to give fleet a whirl, and I know in the background it can use the Language Server Protocol to support many of the languages it currently ships with.

Now it doesn't mean that immediately reading this starter guide, you will have everything under the sun set up with Nix Flakes for your development need. But at least, you won't have to worry about setting up asdf, your weird hacks you need for your machine and the other tiny little things to get elixir started with elixir-ls.

I have a minimal lspconfig with coq_nvim with elixirls and tsserver. The problem is that whenever i code on elixir everything becomes slow.

Well I know one extension that runs your code, elixir-ls. I believe it scans your code and runs dialyzer, a static analysis tool, which runs your code and generates types based on it.

To get started you need a running instance of Livebook

LiveBook site

I prefer functional programming with Livebook[1] for this type of thing. Once you run a cell, it can be published right into a web component as well.

[1] - https://livebook.dev

If you're a coder, Livebook might be worth a look too. I certainly have my eyes on it.

Would highly recommend looking at Jose's use of livebook to answer these. It makes testing easier. It's old but still relevant. Video link inside

That's hard to say. Racket is a rather complete language, as is F# and Elixir. And F# and Racket are extremely capable multi-paradigm languages, supporting basically any paradigm. Elixir is a bit more restricted in terms of its paradigms, but that's a feature oftentimes, and it also makes up for it with its process framework and deep VM support from the BEAM.

I would say that the key difference is that F# and Elixir are backed by industry whereas Racket is primarily backed via academia. Thus, the incentives and goals are more aligned for F# and Elixir to be used in industrial settings.

Also, both F# and Elixir gain a lot from their host VMs in the CLR and BEAM. Overall, F# is the cleanest language of the three, as it is easy to write concise imperative, functional, or OOP code and has easy asynchronous facilities. Elixir supports macros, and although Racket's macro system is far more advanced, I don't think it really provides any measurable utility over Elixir's. I would also say that F# and Elixir's documentation is better than Racket's. Racket has a lot of documentation, but it can be a little terse at times. And Elixir definitely has the most active, vibrant, and complete ecosystem of all three languages, as well as job market.

The last thing is that F# and Elixir have extremely good notebook implementations in Polyglot Notebooks (https://marketplace.visualstudio.com/items?itemName=ms-dotne...) and Livebook (https://livebook.dev/), respectively. I would say both of these exceed the standard Python Jupyter notebook, and Racket doesn't have anything like Polyglot Notebooks or Livebook. (As an aside, it's possible for someone to implement a Racket kernel for Polyglot Notebooks, so maybe that's a good side project for me.)

So for me, over time, it has slowly whittled down to F# and Elixir being my two languages that I reach for to handle effectively any project. Racket just doesn't pull me in that direction, and I would say that Racket is a bit too locked to DrRacket. I tried doing some GUI stuff in Racket, and despite it having an already built framework, I have actually found it easier to write my own due to bugs found and the poor performance of Racket Draw.

This looks very similar to LiveBook¹. It is purely Elixir/BEAM based, but is quite polished and seems like a perfect workflow tool that is also able to expose these workflows (simply called livebooks) as web apps that some functional, non-technical person can execute on his/her own.

1: https://livebook.dev/