>designed specifically around async like Go is, which some profound tradeoffs to make it happen. Go was not designed around the idea of "async". Its goroutine

>designed specifically around async like Go is, which some profound tradeoffs to make it happen. Go was not designed around the idea of "async". Its goroutine approach was inspired by https://en.wikipedia.org/wiki/Communicating_sequential_processes https://en.wikipedia.org/wiki/Communicating_sequential_proce..., a nice theoretical model for concurrency.