Does anyone have a counterpoint to this article about why not to use Elixir?
We're pretty deep into using native erlang for our work so I don't know how much benefit we'd squeeze out of a switch to Elixir, but this is quite intriguing.
BTW, thanks so much for the mention. The core of Kazoo is an all Erlang Stack and we're proud of it (before anyone jumps at me FreeSWITCH is not written in Erlang but it's also not something we at 2600hz wrote). Building the sorts of massively scalable infrastructures we want with the uptime requirements we need would be much harder without the awesome concurrency tools Erlang provides.
Delighted that people care about these kinds of languages :D.
Disclaimer: I am the Community manager for http://www.2600hz.com and the Kazoo Product.
Yes, there's one reason not to use Elixir that I know of: [Edit: It appears I might be wrong on this.]
It doesn't fully cover the erlang syntax. There are a few things you can do in erlang that you can't in elixir.
As I understand it, this will be resolved relatively soon, in an upcoming release, possibly only in a matter of months.
Elixir and erlang can be mixed pretty easily, so there's no harm in trying a module in elixir just to see how you like it. Underneath, it's "erlang all the way down", so you're unlikely to run into problems.
I don't know. I'm new to the language, and after doing the "crash course for erlang developers" and reading the release notes about a month ago, I believe I read that there wasn't full coverage, and that it was expected in 8.0 (or maybe 7.4?)
You probably have forgotten more than I know about this language, so I'm just going to assume I'm mistaken (or was reading something out of date.)
We're pretty deep into using native erlang for our work so I don't know how much benefit we'd squeeze out of a switch to Elixir, but this is quite intriguing.
BTW, thanks so much for the mention. The core of Kazoo is an all Erlang Stack and we're proud of it (before anyone jumps at me FreeSWITCH is not written in Erlang but it's also not something we at 2600hz wrote). Building the sorts of massively scalable infrastructures we want with the uptime requirements we need would be much harder without the awesome concurrency tools Erlang provides.
Delighted that people care about these kinds of languages :D.
Disclaimer: I am the Community manager for http://www.2600hz.com and the Kazoo Product.