I actually think that's not a "Python" or "Go" success story. It's a story of how both of them lack something significant: Python lacks speed and light memory usage, Go lacks dev speed and expresiveness. There is no reason why a single modern language can't combine them, and that would be much better than managing a codebase in two languages, so it's a success story of a useful compromise
I am disagreeing with the parent's point. His point is that Python is better for prototyping which implies that in the beginning people can be quite more productive with it.
I write Python in my day job, and I also experience a velocity boost by using Go. It's easy like Python, but the tooling is better. I really find myself appreciating the static type system catching errors at compile time instead of runtime. And the performance improvements I've observed for the systems I've migrated to Go is 50-300X.
I picked up python and Go at the same time. Go is much easier, logical, faster, uses less memory, and has common-sense stuff like unicode handling built-in.
I only use Python for the same reason I use Java: all the NLP / ML frameworks built by people who don't know Go yet.
Go is nice for its niche, and it can be very cool after using Python. Still it feels too simplistic and limited as a language to me, which includes the "low level" part: it's not "optimally" fast and it's not very easy to interop with other languages
