Hacker News Reader

Comment by p-e-w | Hacker News Reader

The implication in the blog post that Google developers somehow “overlooked” or “misunderstood” important use cases here, and if only they were informed about them they would reconsider, is frankly insulting.

View on HN

Every single time any story has the words "Google developers" in it, they're behaving like arrogant, disconnected, anti-consumer jerks. From constant GCP breakage, to not acknowledging obvious Android bugs, to intentionally braking Chrome. It's a stark contrast to behind the scenes interactions with them.

Yeah, my favorite one is how Chrome users are not smart enough to handle case-aware web-page search toggle. Although to be fair their Chrome team is very arrogant even by Google standards.

If I didn't word it like that (I'm the author) the "reddit mob" would have exploded the thread. That's the last thing I want. I want valuable feedback there, for now its somehwat working.

Most of the users who saw the post on reddit didn't even open the blog post anyways, according to analytics.

Exhibit A: https://issues.chromium.org/issues/40093420

Decades of people desperate for a fix, utter stonewall from Google

Some PM somewhere decided that autocomplete belongs on all your fields, and who are you, the poor site developer, to disagree?

I don't think the developers are bad, the problem are the top dogs that are telling them what to do.

Reply on news.ycombinator.com