[erlang-questions] What do you like the most about Erlang/OTP?

[Erik Søe Sørensen]

One thing I've found useful is the ease of having small embedded DSLs --
data-driven code, also known as. Writing small interpreters can do wonders
sometimes, and is easy in Erlang.
Here @work we used that for a project were we needed a set of
heuristics-based data transformation - "if the data has this form, apply
that transformation". And I've also written data-driven unit tests.
Erlang's literals are fairly good for this.
The generators of QuickCheck and its kin are another example of this.

(Erlang's far from unique wrt this, but it's a thing to like nonetheless.
Scala and Haskell are stronger at DSLs in some respects, I believe -- but I
don't think they have something like file:consult/1.)

And, as others have mentioned: good, strong encapsulation, in the form of
immutable values and process-level isolation - encourages separation of
concerns, increasing the chance of understandable code.

2012/8/27 Loïc Hoguin <essen@REDACTED>

> Hello,
>
> I am wondering what you guys like the most about Erlang/OTP, especially
> newcomers, maybe it changed your life, allowed you to climb the Everest (or
> at least sleep at night).
>
> I'll be synthesizing that into a few key points that I am hopeful will be
> reusable by anyone wanting to sell Erlang to their friends/work/clients.
>
> So help me by telling us what's so good about it!
>
> Thanks.
>
> --
> Loïc Hoguin
> Erlang Cowboy
> Nine Nines
> http://ninenines.eu
> ______________________________**_________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/**listinfo/erlang-questions<http://erlang.org/mailman/listinfo/erlang-questions>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120829/a809c850/attachment.htm>