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.
replyIf 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.
replyMost of the users who saw the post on reddit didn't even open the blog post anyways, according to analytics.
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.
replyExhibit A: https://issues.chromium.org/issues/40093420
replyDecades 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?
[flagged]
replyYou keep spamming variations of this comment without explaining how could apps actually bypass security without several steps that the user needs to take in order for it to work. Are you just farming down votes for some weird reason or will you finally get to the technical details instead of one-sentence snarks?
replyThe linked bug explains exactly how. The fact that you angrily slam downvotes when you hear something doesn't like doesn't make it "farming", just like rage and rants and bizarre accusations of conspiracy in this comment thread won't change the underlying issues that this is going to fix.
replyYou forgot to ask yourself whose interests are being secured, and who/what is the threat being secured from.
replySecurity is not an unqualified good. It's just mechanism of control.
I'm sure Google considers users having freedom to be a "severe security issue." /s
replythis without the /s
reply