Reading the Erlang ProgProgrammers book by Joe Armstrong made me a better Ruby programmer as it changed my perspective on functional programming and abstractions.
I first reached for Elixir when Ruby couldn't handle large amounts of websocket messages. It really shines in high-concurrency contexts. I also love Phoenix LiveView and have a couple of side-projects running on it.
I think most will agree that it improved on Erlang.
For me as a long-term ruby user, though, elixir is
not quite as elegant as it could or should have been.
Even simple things such as "defmodule Xyz do" feels
weird to me.
Reading the Erlang ProgProgrammers book by Joe Armstrong made me a better Ruby programmer as it changed my perspective on functional programming and abstractions.
I first reached for Elixir when Ruby couldn't handle large amounts of websocket messages. It really shines in high-concurrency contexts. I also love Phoenix LiveView and have a couple of side-projects running on it.
its been fun building a multiagent personal assistant.
(wip, no guarantees, this is the engine i use)
https://github.com/ityonemo/ce_ce
Such a delight to use and the core team seems to always make the right decision.
I'm hoping to find a reason to use it soon.
Do you have a program that doesn't need to run fast?
I actually experimented with using it as a backend for a multiplayer turn based game.
I eventually gave up because it’s a bit too difficult without a team.
It's a good joke but most of my applications are I/O bound. So I use Elixir for performance.
I think most will agree that it improved on Erlang.
For me as a long-term ruby user, though, elixir is not quite as elegant as it could or should have been. Even simple things such as "defmodule Xyz do" feels weird to me.