> However, these programmers aren’t fleeing concurrency itself - they’re fleeing concurrent access to the same data. He's not wrong. Modern real world example

> However, these programmers aren’t fleeing concurrency itself - they’re fleeing concurrent access to the same data. He's not wrong. Modern real world example: Golang authors designed net library in a such way, that everyone who uses it has to think about concurrent access to shared mutable states. Which is hard and unnecessary. Event loops never had this problem, but for some reason got labeled "non idiomatic" by Golang folks. So I had to implement event loop myself.