aochagavia
Two months ago I started working professionally on an Elixir project. I had no previous Elixir experience, but I am picking it up at a reasonable pace (previous experience with Rust, Haskell and non-blocking programming in general have proved very useful). One of the things that I find myself missing is the top-notch IDE support I used to have in C# and Typescript, which gave me an incredible productivity boost and made it possible to find my way in new codebases very quickly. Unfortunately, IDE support for Elixir is quite basic at the moment, and my productivity suffers from it (though the fact that I am still learning the language also accounts for the productivity hit). Did anyone here have to adapt to Elixir coming from statically typed languages with great IDE support? How did you adapt?
Some concrete things that boost my productivity as a programmer, which I find myself missing, are:
- Find all usages of functions, modules, struct fields, etc.
- Rename functions, modules, struct fields, etc and have their usages automatically updated.
- A strict compiler that catches type errors, enabling things like “type-error driven development”, where you change something and chase the compiler errors until everything is fixed (it is almost magical to fix all errors and see that the change you introduced “just works”!).
Without these features, I notice that I am much less confident about changing existing code, which I find problematic, because frequent refactoring is often necessary to keep a codebase healthy. Writing new code is not a problem, though.
For the time being, I am using plain textual search a lot (which doesn’t really cut it given the size of the codebase, but I know of nothing better at the moment), using @spec wherever it makes sense (it is not as nice as proper types, but it helps a bit) and writing tests to ensure everything is working properly (ExUnit is great).
By the way, I understand that many of these features are incredibly complex or even impossible to have in a language such as Elixir, so it is probably not a matter of waiting until the tooling gets better. That is why I am looking for ways to adapt my workflow as a programmer, since I assume I am not the first one to stumble upon these obstacles.
I’m looking forward to your suggestions and insights!
Trending in Questions
Other Trending Topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
cmo
Have you tried intellij with the plug-in?
krstfk
I’d recommend you let it go and use testing (unit testing and property based testing) to get to the same level of confidence. If you write idiomatic elixir/erlang code you’ll end up writing pretty robust code (although it might hard to use OTP abstractions at first).
Neovim’s support for elixir through LSP is pretty good and the IntelliJ plugin is nice.
However when I was taught programming it was with a pencil and paper…
asianfilm
Consider writing your core business logic in Gleam because Elixir is not (and is likely never) going to give you the type-driven development experience of Haskell.
I have a modern 50,000 line Elixir codebase that uses best practices like Credo, Dialyzer and test suites for its core business logic and it never gives me enough refactoring confidence.
I’m considering moving its core business logic to Gleam, which has a lot of Elm influence, and some new IDE support in its latest release (but that aspect is also still a work-in-progress).
AstonJ
Welcome Adolfo!
Something we often tell people coming to Elixir from Ruby is that despite how it looks with the obvious Ruby influence on syntax, Elixir isn’t Ruby and there are some stark and fundamental differences.
So that’s something I would say here too - keep in mind Elixir isn’t C# or Typescript and while you may be leaving some things from those ecosystems behind, you will be gaining others (for instance, whatever the reasons might be why you have found yourself working with Elixir now).
With regards to working with Elixir itself, you might find these threads interesting:
Personally I think neovim is great, and if you want to see it in action (as well as Dialyzer) you may want to go through PragDave’s course:
crova
Take a look at Compilation tracers , it’s not going to be on the IDE but you could probably write a tracer to dump to a file and use your IDE’s
go to file/definitionto jump around.aochagavia
Thanks for your answers! I forgot to mention I am currently using vscode with the ElixirLS and Elixir Test extensions. I assume other IDEs offer a somewhat similar development experience (btw I tried IntelliJ a few months ago, but it didn’t work as smoothly).
Right now it looks like I will need to get used to basic IDE / compiler support and hope the features of the language compensate for that. Some that are already proving very useful are:
My hope is that these and other benefits will in the end outweight the limitations caused by lack of static typing (and the great IDE they usually enable). Thanks to @AstonJ for pointing this out!
Now if anyone has any tricks to keep a codebase maintainable, I’d be glad to hear them (maybe there is a cheat sheet somewhere). One trick I am already applying is to use structs for GenServer state, and pattern match on the struct when handling messages, so you get compiler warnings if you try to access non-existent fields and get autocomplete support in the IDE.
axelson
I’m a big fan of that
A library that I’d recommend you look into if you’re working with a decent sized code base is Boundary: Boundary - enforcing boundaries in Elixir projects
It’s great for enforcing some architecture/boundaries on a code base and it can also generate nice images of the boundaries that you’ve defined in your application.
cjbottaro
Heh, this.
To OP, welcome… and welcome to dynamically typed languages!
For me, Elixir is the perfect balance between Ruby (dynamically typed, interpreted, aka literally zero static analysis) and something like Rust (statically typed, compiled, very strict static analysis). The compiler and dialyzer warnings are enough for me to be happy in dynamically typed land. But it won’t give that ease of refactoring / IDE support as in a static typed language.
ElixirLS in VS Code is pretty awesome though.
cjbottaro
Behaviours (kinda like functional interfaces) are nice also and will generate compiler warnings.
cjbottaro
I have high hopes for the gradual typing systems being worked on. See Gradualizer and Gradient.