The article very clearly promotes Erlang and the actor model too: > The actor model appears much better suited to task-based > parallelism where concurrenc

The article very clearly promotes Erlang and the actor model too: > The actor model appears much better suited to task-based > parallelism where concurrency is important. For example, > Erlang programs control telecom equipment with thousands > of unique requests per minute. Meanwhile, dataflow is > focused on data parallelism where single-job data > processing and analysis performance are the main > concerns. In a sense, they're slightly different > solutions for different domains, although conceptually > similar. [Citation needed] for all that, with a proper point of reference with C or C++, as per my original comment.