Re:The Elixir of concurrency
by avodonosov on Monday May 23, 2016 @05:15PM
(#11757053)
In C the OS process takes place of the Erlang "process". C is designed for multi-process systems (Unix), where a task is often implemented by a number of processes. Upon error the process is terminated, but the system (OS) is never "brought down" by a single failure, remains fully operational and you can retry your command again.
[ Parent
| on HN ]
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.
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
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).
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.
> 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
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.