15:20 : Let your process fail and crash, which will lead to clearing the state and let some other process deal with or reap the failure. The failure is communicated to the reaping process in an asynchronous manner. The reaping process acknowledges this failure and does something. This whole thing is the subject of exception handling. 18:34 : The messages are transmitted (TX'd) between processes using the message mailbox data-structure. The receiving process scans it's mailbox periodically and handles the messages. The messages may be handled based on some priority or metric. These constructs are available in most modern programming languages. One problem with Erlang is it cryptic syntax.
Well you already have concurrency oriented programming languages out there like Concurnas go and use that if you want out of the box solutions to these problems
This is really a great Talk
if messages are delivered at most once and there is no delivery guarantee then how can processes be reliably linked in message chains?
15:20 : Let your process fail and crash, which will lead to clearing the state and let some other process deal with or reap the failure. The failure is communicated to the reaping process in an asynchronous manner. The reaping process acknowledges this failure and does something. This whole thing is the subject of exception handling.
18:34 : The messages are transmitted (TX'd) between processes using the message mailbox data-structure. The receiving process scans it's mailbox periodically and handles the messages. The messages may be handled based on some priority or metric.
These constructs are available in most modern programming languages. One problem with Erlang is it cryptic syntax.
)@6-$
Which programming languages implement these features beyond the Erlang VM?
Well you already have concurrency oriented programming languages out there like Concurnas go and use that if you want out of the box solutions to these problems
erlang is older than Concurnas :D