More generally, I use async Python features and libraries, which are developing and changing very quickly. Most stack overflow answers on things like this are at least partially outdated, many more-so. I tend to go to prominent async libraries source code & Github issues to see how the leading users of async features are doing it.
I love reading the docs and using issues.
I work in web so basically anything NPM related (most of the web in my field) is all on GitHub. Much faster than StackOverflow for sure over the past few years. I now read SO mostly to shoot the crap. GitHub has a hold of the latest issues by far. JS being the wild west with guns blazing in the air, has done really well for GitHub.
I also think people raise good points about Microsoft acquiring SO. They are buying up all the developer circles.
Personally, I hope the license thing bites Mr. Spolsky. I think he deserves it after speaking out publicly about getting companies to squash our creative freedoms at home. I'm sorry Joel, not everybody wishes to work 14 hour days for somebody else's vision.
StackOverflow's surplus of dickhead programmers doesn't help either. We don't hide behind usernames on GitHub.
What did he say / where could I read it?
For help with libraries, it makes sense kind of. But I personally wouldn't want to file an issue unless I was sure there was an actual issue. "I don't know how to use it" isn't an issue.
I don't really see what is so horrible about these answers?
I got a clear, concise, and correct answer. I've heard a lot of noise about the toxic community on SO, but I never see it whenever I'm there. Or maybe it's me. Anyway, SO is a very useful resource for me, even at this late date.