I write a lot of code in the "Python would be really chugging here, though it would get the job done if you put a bit of elbow grease into it, but Go chows right through this no problem with no special effort" space. I'm not generally in the "keeping 100 servers 90% occupied space" but it wouldn't take much more in percentage terms for me to fall off of Python. Python's slowness is definitely real, as well as its general difficulty in keeping multiple CPUs going. (Python has a lot of solutions to this problem precisely because none of them are really all that good, compared to language that is 1. compiled and 2. has a solid threading story. It wouldn't have many solutions if one of them was an actual solution to the problem.)
It isn't just Python. I'm getting moved more into a PHP area right now, and there's a system in there that I need to analyze to see whether its performance problems are architectural, or if it's just not a task PHP should be doing and Go(/Rust/C#/Java/... Go is just the one of that set most in my and my team's toolbelt) would actually perform just fine. I don't know which it is yet, but based on what I know at the moment, both are plausible.
And I'm not a "hater". I just have a clear view of the tradeoffs involved. There are many tasks for which Python is more power than one knows what to do with. Computers have gotten pretty fast.
It isn't just Python. I'm getting moved more into a PHP area right now, and there's a system in there that I need to analyze to see whether its performance problems are architectural, or if it's just not a task PHP should be doing and Go(/Rust/C#/Java/... Go is just the one of that set most in my and my team's toolbelt) would actually perform just fine. I don't know which it is yet, but based on what I know at the moment, both are plausible.
And I'm not a "hater". I just have a clear view of the tradeoffs involved. There are many tasks for which Python is more power than one knows what to do with. Computers have gotten pretty fast.