News for hackers. Stuff that matters.
Re:Elixir v1.1.0 Released by sinatra on Friday September 25, 2015 @11:19AM (#10278638)
IMHO the main reasons compared to, say Ruby, would be: native support for concurrency, Erlang VM, fault tolerance and speed. However, I'm also disappointed that there's no type checking. EDIT: Although I don't agree with the comment below, I'm removing comment about Golang because it's unnecessary in the discussion about Elixir.
Re:Elixir v1.1.0 Released by eatonphil on Friday September 25, 2015 @11:24AM (#10278656)
I'm not calling you out, but in general when I hear people compare Go to languages with more "intense" typing (including Erlang, though possibly not Elixir) I find it funny. Go has a very crude type system and can be more easily compared to C (in terms of types) than anything else I think.

If you ever try to do anything as interesting with types as you could in a dynamic language, you'd immediately start transporting interface{}s (essentially void*) all over the place and lose all static typing [0] (and context[1]).

[0] - https://github.com/eatonphil/gimpy/blob/master/net/http/http...

[1] - https://github.com/eatonphil/gimpy

Re:Elixir v1.1.0 Released by dragonwriter on Friday September 25, 2015 @03:08PM (#10280059)
> IMHO the main reasons compared to, say Ruby, would be: native support for concurrency, Erlang VM, fault tolerance and speed. However, I'm also disappointed that there's no type checking.

You should check out Dialyzer.

Re:Elixir v1.1.0 Released by 15155 on Friday September 25, 2015 @04:16PM (#10280449)
The thing that always kills me with Dialyzer is that it's just not an ML.