Chromium uses actor model extensively. Yet in Safari Apple moves into the direction of multiple fine-grain locks for performance reasons I presume. So it unclea

Chromium uses actor model extensively. Yet in Safari Apple moves into the direction of multiple fine-grain locks for performance reasons I presume. So it unclear which model will dominate the industry. Locks allow for better performance, but the code becomes much harder to maintain and reason about, although even in C++ with the right API and proper discipline the situation is not that bad. Also it is interesting that Go does not use the actor model with its strictly one polymorphic message queue per sequence or green thread. Rather it is based on CSP or concurrent sequential processes with green threads with multiple typed message queues or channels per thread. In my limited experience with Go I would rather use a third-party actor model implementation rather than native CSP as the programming model is simpler.