> Those are all different kinds of “it” with differences which affect your application design. "It" here is concurrency, and Go proves that its possible for a

> Those are all different kinds of “it” with differences which affect your application design. "It" here is concurrency, and Go proves that its possible for a language to have "one way to do it". Goroutines are often seen as an alternative to async/await, but they're also a better parallelism solution than all of Python's threading, multiprocessing and subinterpreters. > If you want a stronger criticism, pick multiprocessing/threading and concurrent, and the long migration trajectory for deprecating the older ones. I haven't heard anything about deprecating multiprocessing/threading. Is that the long-term plan for subinterpreters?