I don't buy these arguments. You hit on a pathological case in Go where Python managed to be faster. That's not remotely typical, and even the "just use C/Cytho

I don't buy these arguments. You hit on a pathological case in Go where Python managed to be faster. That's not remotely typical, and even the "just use C/Cython/Numpy" is a huge oversell--there are some problems that are amenable to dropping into a lower level language, but many more are not. At best, it's just very, very hard to make Python as fast as unoptimized Go. Besides performance, CGo and tooling seem to make up the bulk of your criticisms. I agree that Python's C interop story is strictly better than Go's, but this seems like throwing the baby out with the bathwater for a huge suite of applications. I also strongly disagree that Python's tooling is better; I think your 20 years of experience with it has biased you against the frustrations the rest of us have when we try to pick it up. By contrast, I've found Go's tooling to be superb--profiling, testing, benchmarking, documentation, etc all included out of the box. There are still holes (like debugging), but I daresay Go's tooling is categorically better than Python's.