[erlang-questions] Any Erlang Devs Contemplating Elixir?

Zachary Kessin <>
Sun Mar 6 20:06:14 CET 2016


I started a new project a while ago, and I am using Erlang + Webmachine as
it is what I am familiar with. Elixir has some cool stuff going on, but as
I was already using 1 language that I was not familiar with (Elm) I didn't
want to add to the technical risk by adding a 2nd language when the
benefits of Elixir over Erlang for me were not that huge.

Of course it is possible that in the future some Elixir may be added to the
project, but who knows.

I for one would love to see an ML-family language on the beam!
ᐧ

On Sun, Mar 6, 2016 at 6:32 PM, Garrett Smith <> wrote:

> On Sat, Mar 5, 2016 at 10:04 PM Robert Virding <> wrote:
>
>> One definite benefit in having to explicitly write every callback even if
>> it is doing "default" stuff is that everything *IS* then explicit and you
>> can directly SEE what happens. And come on, writing a 2 line default case
>> for a few callbacks is really not that much to extra code.
>>
>> A major problem with having implicit "default" cases is that what people
>> consider to be a reasonable default handling varies depending on what just
>> that server is doing. There is no default that suits every server so I will
>> probably have to write it out and anyway.
>>
>> Hiding callbacks behind defaults also means that you don't SEE everything
>> that is there. This can be a major problem for newcomers.
>>
>
> A counter point to this is that by deferring increasingly complex cases by
> providing sensible defaults, a user can more quickly and correctly
> understand an API. A useful abstraction has a story line - and I think the
> simpler the better. Requiring the user to accommodate increasingly edge
> cases undermines the main story line.
>
> E.g. I like the pattern in Erlang functions that follows the getopt Tao of
> required params + options. Let me get to the gist of an operation with the
> fewest possible inputs and I can incrementally grow into the more complex
> cases.
>
> I think this is less about typing and more about clarity of intent.
>
> The challenge to getting this right is drawing that line between the
> essential interface and the incremental enhancements. Libraries fail when
> they outright hide important details and leave the user mystified with
> seemingly magical behavior.
>
>
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
>
>


-- 
Zach Kessin
Your CRM Link
<http://yourcrm.link/?utm_source=email%20signature&utm_medium=email&utm_campaign=passive>
Twitter: @zkessin <https://twitter.com/zkessin>
Skype: zachkessin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160306/5d32acaa/attachment.html>


More information about the erlang-questions mailing list