Articles like this are declaring issues in existing communities. This make it natural for members in those communities to create opinions and question when listening, internalizing, and cultivating the issues brought forth. Some of those opinions will be of the type "Is this issue, compared to all other form of issues already identified in the community, significant different that it need a imminent and unique reaction?".
Hackers/programers/scientists/problem solvers is also extremely, to the point of obsession, interested in identify root issues when talking about problems. To find root issues, one need to ask questions, like are there similar issues like this one? Are they caused by the same problem? What suggested fixes are there? are those proven to work? whats does the number says, do they show a trend? are there sources that back up what people experience? How can we eliminate research and political biases? are there additional factors involved like relative risk, risk assessment and risk aversion?
Denying those questions and asking the community to accept the issues as facts, immune against research and question, and just shut-up and follow any suggested fixes it gets, is wrong. Just simply wrong. Maybe that will result in people dropping out, showing up in small numbers, or who starts making their own exclusive conferences/coding groups/fill-in-the-blank. Maybe. But maybe the better way is to ask the questions and find the answers?