[<<][softarch][>>][..]Thu Nov 14 07:57:14 EST 2019
Because if done well, it can be cheap. But the main reason is that the need for parallelism will arise at some point, and it is better to ALWAYS think in terms of transactions. Explicit message handling solves that. In this sense, Erlang's supervisor trees are there to restore macro objects: objects that are built from interacting sub-objects.
[Reply][About]
[<<][softarch][>>][..]