Re:Why Python Is Slow: Looking Under the Hood (2014)
by BuckRogers on Saturday July 09, 2016 @02:45AM
(#12060443)
My largest Go project has been 40KLOC, after which I felt that Python would've been at least 25% more productive.
The next-step isn't Go. It's Elixir. Or Rust if you need a systems language.
Go's biggest problem is a lack of generics, which means that in some cases, you have to fall back to duck typing. So the worst case is no worse than Python's best case.