Why Elixir Is the Best Language for Building a Bootstrapped, B2B SaaS in 2024
Advocates of Elixir and its Phoenix/LiveView stack argue it’s highly productive, performant, and well-suited to real‑time, stateful web applications, making it attractive for bootstrapped B2B SaaS. Others counter that mature ecosystems like Rails and Django still offer faster feature delivery, richer libraries, and a much larger hiring pool—critical factors when scaling a product or team. Several commenters also stress that full rewrites into Elixir can be a poor business tradeoff, and that LiveView’s server‑centric model carries real limitations for high-latency or offline use cases despite the hype.
Elixir/Phoenix vs Rails/Django/Laravel for Bootstrapped SaaS
- Several commenters moved from PHP/Laravel or Rails to Elixir/Phoenix and now strongly prefer it, especially for maintainability, runtime performance, and realtime features.
- Others argue Rails and Django still win for bootstrapping: larger ecosystems, more “drop‑in” solutions, more examples, and easier hiring.
- Some say Phoenix productivity now matches Rails for typical CRUD apps; where complexity and concurrency grow, many feel Elixir pulls ahead.
- A few note that for simple web pages and standard business logic, Django/Rails are “by far the best,” with Elixir better when there is long‑running, concurrent, or realtime server work.
LiveView, Livewire, and Realtime
- LiveView is widely praised as faster, more reliable, and less “magical” than Laravel Livewire, with better performance due to persistent server processes and diff‑based WebSocket updates.
- Rails’ evolving realtime story (e.g., Turbo) is mentioned, but several argue Phoenix still “demolishes” Rails in realtime and concurrent connection handling.
- Some warn that LiveView is a poor fit for high‑latency clients or offline/“must work without server” scenarios.
Rewrites vs Business Outcomes
- Strong caution against full rewrites of existing products into Elixir (or anything): time spent reproducing features can significantly hurt business outcomes.
- Incremental migrations and focusing on customer‑visible features are repeatedly recommended.
- Some counter that targeted rewrites or migrations can pay off when legacy systems are extremely brittle, but scope control is critical.
Hiring, Team Scaling, and Ecosystem
- Mixed reports on hiring: some say Elixir devs are rare and expensive; others report many qualified applicants via Elixir‑specific channels.
- Common theme: Elixir devs tend to be senior “refugees” from other stacks; smaller, high‑leverage teams are seen as the norm.
- Concern that scaling from a tiny team to tens or hundreds of engineers is harder with Elixir than with mainstream stacks; others argue you rarely need that many Elixir devs if the system is well‑designed.
Community, Documentation, and Hype
- Many praise the language, Phoenix docs, and core books; others feel the public ecosystem lacks depth beyond intros and core tools.
- Some are tired of “why I chose Elixir” hype posts and want more case studies and concrete “here’s what we built and how it worked out.”