Why I’m betting on Elixir

The author says Elixir won him over after years of building Ruby on Rails applications. He compares Ruby’s impact on web development with what he expects from Elixir and Phoenix, especially because they keep the focus on developer happiness while adding concurrency, fault tolerance, and speed.

Reading notes

#

• Ruby and Rails changed web development by prioritizing developer happiness, productivity, and testing.
• The author mentions memory problems in Rails apps, including restarts and worker-killer workarounds.
• He says he has never used threads in production Rails apps and prefers background job systems like Sidekiq or Resque.
• He describes test suites that took more than 20 minutes and startup times of about 40 seconds, then praises Zeus for speeding up Rails boot time.
• He liked Scala’s pattern matching and concurrency story, but disliked JVM package management and the Java-oriented ecosystem around it.
• He presents Mix as Elixir’s package tool and says it feels as good to use as Bundler and Rake.
• He highlights Erlang’s emphasis on functional programming, fault tolerance, and scalability, and connects those values to Elixir.
• He says Phoenix feels similar to Rails, uses WebSockets through channels, and runs very fast.
• He credits leadership from people like José Valim and Chris McCord as part of what makes the Elixir community strong.
• He concludes that the web is entering a new phase where Elixir and Phoenix can have an impact similar to Rails.