The Elixir of concurrency

Re:The Elixir of concurrency by honua on Monday May 23, 2016 @08:45PM (#11758147)

While similar, it's not the same. Erlang/OTP/Elixir provides baked in tools to watch, restart, etc. processes. In C you'd need to do this yourself.

[ Parent | on HN ]

Re:The Elixir of concurrency by avodonosov on Monday May 23, 2016 @09:21PM (#11758327)

The tools to watch, restart, etc are bash, ps, top, etc

[ Parent | on HN ]

Re:The Elixir of concurrency by dozzie on Tuesday May 24, 2016 @06:07AM (#11760176)

Not really. Those are equivalent to monitors and links in Erlang/BEAM, if we go this line of thought. OTP is a collection of architectural patterns coded down in Erlang (what means OTP is a framework).

[ Parent | on HN ]

Re:The Elixir of concurrency by avodonosov on Tuesday May 24, 2016 @06:34PM (#11766081)

We are talking about error handling. My point: "let it crash" aka "failstop principle" is well known for decades, and practiced in all major languages.

[ Parent | on HN ]

Re:The Elixir of concurrency by dozzie on Tuesday May 24, 2016 @06:40PM (#11766132)

> We are talking about error handling.

I thought we switched to a little more down-in-the-trenches discussion with you saying:

> The tools to watch, restart, etc are bash, ps, top, etc

[ Parent | on HN ]

Re:The Elixir of concurrency by avodonosov on Tuesday May 24, 2016 @06:46PM (#11766180)

Carried away a little. Not to say it's not interesting to compare Unix/C programs with OTP/Erlang, but it's a different subject.

[ Parent | on HN ]