> Async way is not the only way to create event based systems.
Of course it isn't. But it works well in Erlang thanks to many other aspects
("crash-only" error handling style, supervision trees, supercheap threads,
message passing and matching). Some of these are less useful for e.g. GUI -- at
least, I haven't seem them applied in a way that is both convenient and
provides a reasonable experience.
I've dabbled in Erlang, do not claim to be an expert, and would love to be
proven wrong -- and when I am proved wrong about this, there's still all of
these other features which are more than just "library level" that make Erlang
what it is - they go through the entire runtime, ecosystem, and culture.
Adopting only the actor model without them is unlikely to deliver the same
robustness and ease you get in Erlang.
