updated on
June 1st, 2023
approx reading time
4 Minutes
Abstract Elixir, a dynamic, functional language built on the Erlang VM (BEAM), has gained significant traction for building scalable, fault-tolerant applications. However, its unique macro system, pipe operator, and OTP (Open Telecom Platform) behaviours present challenges for tooling. This paper explores the state of Elixir support within JetBrains IDEs (IntelliJ IDEA, Rider, WebStorm). It traces the evolution from community-driven plugins to the official "IntelliJ Elixir" plugin, analyzes its core features (code insight, refactoring, debugging), compares it with the dominant competitor (Visual Studio Code + ElixirLS), and evaluates its role in professional Elixir development. The paper concludes that while the JetBrains plugin offers a superior refactoring and navigation experience for monorepo and umbrella apps, the community’s momentum behind ElixirLS on VS Code remains a critical counterweight. 1. Introduction Elixir’s rise is attributable to three pillars: Ruby-like syntax, Erlang’s actor-based concurrency, and the Phoenix web framework’s real-time capabilities. As Elixir enters enterprise environments (e.g., Discord, PepsiCo, Brex), the demand for robust IDEs has grown.
The two tools serve different stages of the development lifecycle: VS Code/ElixirLS for rapid iteration, debugging, and macro exploration; JetBrains for large-scale code maintenance and architectural refactoring. Rather than a winner-takes-all market, the Elixir community benefits from this diversity. Future convergence via LSP adoption in JetBrains could ultimately provide developers with the best of both worlds.
IntelliJ: Set breakpoint in handle_call . Run mix debug . Variables show in UI, but inspection of state map sometimes truncates large values. Stepping into :gen_server internal code is possible but verbose.
In VS Code: Manually search-replace, or use LSP rename (which often misses references in umbrella children due to path misconfiguration). Risk of broken code.
VS Code highlights type warnings from Dialyzer. JetBrains requires external tool or manual Dialyzer run.
JetBrains, known for language-aware IDEs (IntelliJ IDEA, PyCharm, GoLand), offers a unique proposition: deep static analysis, structural search and replace, and VCS integration. However, Elixir’s dynamic nature and compile-time macros challenge traditional static analysis. This paper investigates how JetBrains’ architecture adapts to Elixir, and whether its approach yields tangible productivity gains.
updated on
June 1st, 2023
approx reading time
4 Minutes
Abstract Elixir, a dynamic, functional language built on the Erlang VM (BEAM), has gained significant traction for building scalable, fault-tolerant applications. However, its unique macro system, pipe operator, and OTP (Open Telecom Platform) behaviours present challenges for tooling. This paper explores the state of Elixir support within JetBrains IDEs (IntelliJ IDEA, Rider, WebStorm). It traces the evolution from community-driven plugins to the official "IntelliJ Elixir" plugin, analyzes its core features (code insight, refactoring, debugging), compares it with the dominant competitor (Visual Studio Code + ElixirLS), and evaluates its role in professional Elixir development. The paper concludes that while the JetBrains plugin offers a superior refactoring and navigation experience for monorepo and umbrella apps, the community’s momentum behind ElixirLS on VS Code remains a critical counterweight. 1. Introduction Elixir’s rise is attributable to three pillars: Ruby-like syntax, Erlang’s actor-based concurrency, and the Phoenix web framework’s real-time capabilities. As Elixir enters enterprise environments (e.g., Discord, PepsiCo, Brex), the demand for robust IDEs has grown.
The two tools serve different stages of the development lifecycle: VS Code/ElixirLS for rapid iteration, debugging, and macro exploration; JetBrains for large-scale code maintenance and architectural refactoring. Rather than a winner-takes-all market, the Elixir community benefits from this diversity. Future convergence via LSP adoption in JetBrains could ultimately provide developers with the best of both worlds.
IntelliJ: Set breakpoint in handle_call . Run mix debug . Variables show in UI, but inspection of state map sometimes truncates large values. Stepping into :gen_server internal code is possible but verbose.
In VS Code: Manually search-replace, or use LSP rename (which often misses references in umbrella children due to path misconfiguration). Risk of broken code.
VS Code highlights type warnings from Dialyzer. JetBrains requires external tool or manual Dialyzer run.
JetBrains, known for language-aware IDEs (IntelliJ IDEA, PyCharm, GoLand), offers a unique proposition: deep static analysis, structural search and replace, and VCS integration. However, Elixir’s dynamic nature and compile-time macros challenge traditional static analysis. This paper investigates how JetBrains’ architecture adapts to Elixir, and whether its approach yields tangible productivity gains.
Your hub for everything you need to know about simulation and the world of CAE
Sign up for SimScale
and start simulating now
