With the challenges facing Ruby and Rails, many are finding Elixir as a good alternative, especially considering performance and concurrency.
But this isn't just because it has a faster interpreter--it is more memory efficient, better with streams, parallel and concurrent than Ruby, and this means you typically have better applications. But if you are just doing CPU bound things, they probably will bench roughly equivalently.
To help people explore possibilities with Elixir, I've gathered some information together.
Elixir looks a lot like Ruby, by design, but it runs on top of the Erlang beam, which has existed for some time--this has influenced its behavior and concepts, to a degree. This also means there are some packages that can be leveraged across both platforms.
- Elixir for Rubyists
- Elixir the New Wave?
- When to use Elixir vs Ruby/Rails
- Language Constructs are different:
- Iterating is different
- Pattern Matching is a very powerful polymorphism - think of it as describing how you want to see your data before the function is called, rather than poking and investigating the data after it arrives to decide if you like it's shape.
- Phoenix rather than Rails
- Phoenix for Rails Developers (book)
- Understand Elixir Processes - how to leverage the power of Elixir's concurrency.
- Understanding Supervisors
- Using the system:
- Who uses Elixir?