> However, some people prefer those libraries. Which is fine. They both exist, use what you like. There's no need to have wars about it. This results in ecosys

> However, some people prefer those libraries. Which is fine. They both exist, use what you like. There's no need to have wars about it. This results in ecosystem fragmentation though, which means that more effort is spent developing and maintaining different kind of solutions to the same problem, only because of their different developer experience. On the contrary, look at Go, where it was decided from the beginning (i.e. stdlib) that we're going with coroutines. It's a bit like (I'm exaggerating) arguing for what should be the default coding style, where a built-in/blessed formatter would make this a non-issue. gofmt is a nice example of this. Also, honest question: AFAICT Python was more of the "there's 1 preferred way to do things". Doesn't arguing between async and coroutines goes against this mantra?