> However, most programmers, and programming languages, remain stuck in a serial-by-default paradigm You still have to decide upon the unit of work that is goi

> However, most programmers, and programming languages, remain stuck in a serial-by-default paradigm You still have to decide upon the unit of work that is going to be sent to a different thread/core/processor/NUMA node/whatever. The different units of work that are distributed should not share state; one really doesn't want to be sharing a lot of state between different processors, because synchronizing the processors memory caches in NUMA is a extremely slow. I guess it is really hard to break up both the program and data and decide upon the optimal granularity of the work units, it is not something that can be easily done behind the scenes - human intervention is still required.