> Then, an opportunity arose to use Elixir but, because of its early stage (this was right between 0.3 and 0.4), I couldn't deploy it in a production environment, so I ended up choosing Clojure.
At the time (and still today) I would probably have done the same. We still need a couple more months before we can stamp "Production Ready" in it.
> No need to; one could just adapt ClojureScript to spit out Erlang. It would depend on the JVM and wouldn't support native macros, but it would work ok, I guess.
I guess I can eventually take a look at this as well for fun. :)
> I understand it might be premature, but I would love to know what kind of projects/developers is Elixir attracting?
My background is web development, so expect something in this area in the future. It always amazes me how people like the What's App guys can get 2 million TCP connections in a single Erlang node (source: http://blog.whatsapp.com/index.php/2012/01/1-million-is-so-2...). With web sockets and native clients becoming more and more common, having powerful abstractions around TCP connections seems like a good idea.
At the time (and still today) I would probably have done the same. We still need a couple more months before we can stamp "Production Ready" in it.
> No need to; one could just adapt ClojureScript to spit out Erlang. It would depend on the JVM and wouldn't support native macros, but it would work ok, I guess.
I guess I can eventually take a look at this as well for fun. :)
> I understand it might be premature, but I would love to know what kind of projects/developers is Elixir attracting?
My background is web development, so expect something in this area in the future. It always amazes me how people like the What's App guys can get 2 million TCP connections in a single Erlang node (source: http://blog.whatsapp.com/index.php/2012/01/1-million-is-so-2...). With web sockets and native clients becoming more and more common, having powerful abstractions around TCP connections seems like a good idea.