I see your point, I still disagree, I encountered some bugs that were incredibly surprising with postgres + sidekiq combo (made perfect sense though)
Elixir doesn't distribute anything unless you tell it to, keep that in mind. You can run it like a normal rails app.
The OTP by default runs on one machine and as such, it's not subject to distributed systems law.
And you can still scale horizontally in the traditional way (deploy the app to multiple machines), no need to learn or use the multi-nodes.
The debugging experience is the same.
Of course you have to learn the OTP library at some point, but it's equivalent to study the ruby standard library: it's natural, must be done, like for any programming language.
That being said, the tools provided are really nice, given erlang is very old, the tools do exist.
And you can connect to a production machine with an "irb session", except that the one in elixir is in the same memory space as the main process, so you can actually inspect in memory stuff, very powerful and dangerous.
Elixir doesn't distribute anything unless you tell it to, keep that in mind. You can run it like a normal rails app. The OTP by default runs on one machine and as such, it's not subject to distributed systems law.
And you can still scale horizontally in the traditional way (deploy the app to multiple machines), no need to learn or use the multi-nodes.
The debugging experience is the same. Of course you have to learn the OTP library at some point, but it's equivalent to study the ruby standard library: it's natural, must be done, like for any programming language.
That being said, the tools provided are really nice, given erlang is very old, the tools do exist. And you can connect to a production machine with an "irb session", except that the one in elixir is in the same memory space as the main process, so you can actually inspect in memory stuff, very powerful and dangerous.