"with a good concurrency model, making your program comparatively easy to parallelize on a per-function basis" Actually Go's shared-memory multithreading concu

"with a good concurrency model, making your program comparatively easy to parallelize on a per-function basis" Actually Go's shared-memory multithreading concurrency model encourages program architectures that are not easily parallelizable at all. And it's harmful to praise it. We have much better share-nothing models that encourage parallelizable programs from the start.