Go has pretty neat semantics for channels and goroutines, but it presumes you want threads and blocking IO. Or in other words, "hey kid here's some rope" Your

Go has pretty neat semantics for channels and goroutines, but it presumes you want threads and blocking IO. Or in other words, "hey kid here's some rope" Your approach to concurrency matters even more than the tool you use, and python is a great tool for network services. It's my preferred tool actually. Maybe it's time to start porting twisted to go.