Elixir Is Erlang, not Ruby

Re:Elixir Is Erlang, not Ruby by josevalim on Monday September 07, 2020 @04:13AM (#24397573)

> Elixir tried to "do away with them" because Elixir thinks they're "confusing" but they're actually really important tools.

That's completely inaccurate. They are an important part of Elixir and they are fully documented.

Elixir even has annotations that allow you to say "this function maps to a behaviour's callback". For example:

    @behaviour GenServer

    @impl true
    def handle_info(msg, state)

Those are important because, with optional callbacks, you can make a typo on the function name or on the number of arguments and you won't get any warning, in both Erlang and Elixir. "@impl true" allows you to close this gap.

So we do support behaviours and we have added more static guarantees compared to what you would find in Erlang.

> The Elixir people really don't understand Erlang very well

It is a bit depressing it has come to this but my long list of contributions to Erlang/OTP through pull requests, discussions, EEPs, etc say otherwise.

[ Parent | on HN ]

Re:Elixir Is Erlang, not Ruby by dynamite-ready on Monday September 07, 2020 @06:02AM (#24398218)

I wouldn't feed the troll. The many people who know and appreciate your language realise how much of an improvement Elixir represents over Erlang.

Including Joe Armstrong himself... https://joearms.github.io/published/2013-05-31-a-week-with-e... ^_^

[ Parent | on HN ]