Earlier quoted context omitted.
Every single Google product is slower on Firefox and it’s hard to not call this malice and artificial. Many people check out Gmail and GMaps on Firefox and go back to Chrome because of their clunkiness on Firefox.
I try out google products on occasion and find them rubbish compared with alternatives, so go back to non-google products.
Chrome phasing out support for User-Agent
161–170 of 329 posts
Re: Chrome phasing out support for User-Agent
#162> https://github.com/WICG/ua-client-hints I don't really understand how this will result in any real difference in privacy or homogeneity of the web. Realistically every browser that implements this is gonna offer up all the info the server asks for because asking the user each time is terrible UX. Additionally this will allow google to further segment out any browser that doesn't implement this because they'll ask f…
> I don't really understand how this will result in any real difference in privacy or homogeneity of the web. It does a little: sites don't passively receive this information all the time, instead they have to actively ask for it. And browsers can say no, much like they can with blocking third party cookies. In any case I'm not sure privacy is the ultimate goal here: it's intended to replace the awful user agent snif…
(Disclosure: I work at Google, speaking only for myself)
Re: Chrome phasing out support for User-Agent
#163Earlier quoted context omitted.
It actually insert a line break on enter, make it invisible and can't be deleted only on firefox. Pretend firefox as chrome makes it works perfectly. They lock the community thread and fixed that after several days I found the finding and post it there. Shame on you, google.
Oh my god. I knew it was inserting a line break when I hit enter but I didn't realize it was a FF only issue. gdi Google.
Re: Chrome phasing out support for User-Agent
#164User-agent is super useful to human people. But corporate people don't have a use for it. They will get that information via running arbitrary code on your insecure browser anyway. So, because mega-corps now define the web (instead of the w3c) this is life. But it doesn't have to be. We don't have to follow Google/Apple-Web standards. Anyone that makes and runs websites has a choice. And every person can simply choic…
Few advertisers rely on user agent for ad targeting since it can be easily mocked with each HTTP request. It is used for fingerprinting, sure, but from my experience, mostly as a way to identify bot traffic.
It is also true that the advertisers that fingerprint people rely on JS that executes WebGL code in order to get data from the machine.
Finally, you are right that it doesn't make sense that a company like Google dictates these standards since they have a conflict of interests worth almost a trillion dollars.
Re: Chrome phasing out support for User-Agent
#165Earlier quoted context omitted.
But, is it really such an improvement ? Or is it just an improvement for Cloud provider that keep pushing the Kool-Aid ? I still see a lot of contradicting benchmark and, apart from some Google Apps, personnally, I have not seen a lot of sites actually really leveraging HTTP2 (including push). But maybe you did put and leverage HTTP2 on your own website ? At your company ? Did you use push ? Do you use it with CDN ?
> But, is it really such an improvement? Yes, unequivocally. It’s amazing, even without push. The websites that use it are faster, and the development process for making apps or sites that load quickly is much more sane. You don’t have to resort to the kind of weird trickery that pervades HTTP/1 apps. > Or is it just an improvement for Cloud provider that keep pushing the Kool-Aid ? I don’t see how that makes any sen…
Are you actually seeing good results from push? I have seen many projects try to use it, but am not aware of any that have ended up keeping it.
(Disclosure: I work at Google)
Re: Chrome phasing out support for User-Agent
#166Earlier quoted context omitted.
Every single Google product is slower on Firefox and it’s hard to not call this malice and artificial. Many people check out Gmail and GMaps on Firefox and go back to Chrome because of their clunkiness on Firefox.
> malice and artificial are you actually asserting that Google is purposefully adding code/"tweaking" their web apps to run slowly on browsers other than Chrome? do you have any evidence at all for this other than anecdotes about people experiencing Google web app clunkiness on Firefox?
Re: Chrome phasing out support for User-Agent
#167Earlier quoted context omitted.
I try out google products on occasion and find them rubbish compared with alternatives, so go back to non-google products.
Regarding google properties what do you prefer and why?
Gmail is painful compared with OWA (work) and zoho (home), I stopped using my gmail account for new stuff about a year ago.
Re: Chrome phasing out support for User-Agent
#168The weird thing about this is that the only company I've seen doing problematic user-agent handling in recent years is Google themselves. They have released several products as Chrome-only, which then turned out to work fine in every other browser if they just pretended to be Chrome through the user agent. Same with their search pages, which on mobile were very bad in every non-Chrome browser purely based on user age…
I had been thinking recently as I've been using Firefox more that Google maps had got clunky. With a little fiddling prompted by your comment, it turns out Maps sniffs specifically to reduce fluid animations on Firefox (and probably some other browsers).
Re: Chrome phasing out support for User-Agent
#169Earlier quoted context omitted.
browser feature detection is the way grown up developers have been doing this for several years now. user agent sniffing is dumb because it bundles a ton of assumptions with a high upkeep requirement, all wrapped up in an unreadable regex. It's been bad practice for ages; I'd be surprised if that's how Amazon is doing it still.
> browser feature detection is the way grown up developers have been doing this for several years now. and how do these grown up developers feature-detect when js is disabled? or are they too "grown up" to deal with anything but the ideal scenario? > I'd be surprised if that's how Amazon is doing it still. why don't you go there and open up your "grown up developer" devtools.
Re: Chrome phasing out support for User-Agent
#170Earlier quoted context omitted.
Every single Google product is slower on Firefox and it’s hard to not call this malice and artificial. Many people check out Gmail and GMaps on Firefox and go back to Chrome because of their clunkiness on Firefox.
> malice and artificial are you actually asserting that Google is purposefully adding code/"tweaking" their web apps to run slowly on browsers other than Chrome? do you have any evidence at all for this other than anecdotes about people experiencing Google web app clunkiness on Firefox?