Unfortunately, Chrome 70 is also when `www` subdomain is slated to get re-hidden, and when web audio breaking changes are slated to get re-introduced. There's just too much to keep up with at this point. I'm happy about this change, it's a big move in the right direction. But it doesn't give me any confidence for the future. It's crazy that users have to do this every single release. It can't continue like this. I ha…
It's not targeted to technical communities. Chrome's market share is 50% and growing. It became successful in the first place because it's fast and simple. It's clearly targeted to average Joe by design, not programmers.
Many of the complaints that Chrome has gotten are not specific to technical communities. People were mad about `www` not because the technical communities have a thing for seeing the subdomains, but because there's a risk that average Joes can be phished when they're removed, and because on some domains the removal makes technical support for people like Joe harder. Similarly, the Web Audio complaints were not merely that the technical community wanted more control, it was that the changes broke the web for non-technical users in a way that commercially advantaged Google's own properties.
Secondly, Google's external PR has never taken this stance. Google invests a lot into interfacing with the dev community and positioning Chrome as a dev-friendly browser. I very much doubt that any Chrome dev on Twitter would agree with what you're saying. They would say that Chrome is trying to be a browser for both casual and advanced users.
As long as Google advertises Chrome that way, I don't see the problem with the technical community demanding a certain level of consideration. How many people on HN use Chrome (or at least did a week ago ;))? If Chrome isn't designed for people like them, than it seems like the obvious solution is for any tech savvy communities to en masse switch to Firefox and do the majority of their development/testing there.
But again, most of the changes that people are mad about aren't tech-specific concerns. I don't use Chrome for daily browsing; I'm mad that Google made a change that made it easier for them to spy on my parents. I'm responsible for protecting them. I'm responsible for mitigating Chrome's technical problems when they impact nontechnical users and customers that I care about.