News for hackers. Stuff that matters.
Re:Chrome phasing out support for User-Agent by blntechie on Wednesday March 25, 2020 @01:47PM (#22686836)
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.
Re:Chrome phasing out support for User-Agent by mindcrime on Wednesday March 25, 2020 @02:47PM (#22687298)
"Google ain't done, till Firefox won't run"?
Re:Chrome phasing out support for User-Agent by ricktdotorg on Wednesday March 25, 2020 @02:20PM (#22687081)
> 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 by izolate on Wednesday March 25, 2020 @02:44PM (#22687267)
It could also be a passive, malicious de-prioritization of bugfixes for Firefox that would cause the same effect. It seems like this would be a more likely scenario.
Re:Chrome phasing out support for User-Agent by sudosysgen on Wednesday March 25, 2020 @03:06PM (#22687472)
I would believe that if changing the user agent or toggling some flags didn't fix it.
Re:Chrome phasing out support for User-Agent by ADefenestrator on Tuesday March 31, 2020 @09:59AM (#22737565)
Probably a lot of the other way around as well. Google employees likely use Chrome and Docs/Sheets heavily, so they get a rapid high-quality feedback loop with any bugs or performance issues affecting the Chrome devs and people around them.
Re:Chrome phasing out support for User-Agent by dijit on Wednesday March 25, 2020 @02:39PM (#22687231)
If there was direct evidence it would warrant its own post, so I think your comment has been made in bad faith since people are talking about their own experiences.

That said; if it's possible to measure firefox/chrome performance (with altered user-agents) it would make for a good blog post.

Re:Chrome phasing out support for User-Agent by adrianmonk on Wednesday March 25, 2020 @03:05PM (#22687455)
How is "hard to not call this malice and artificial" people talking about their own experiences?
Re:Chrome phasing out support for User-Agent by Talanes on Wednesday March 25, 2020 @03:38PM (#22687767)
The "hard not to call" portion takes it from the realm of objective fact and into subjective measure.
Re:Chrome phasing out support for User-Agent by adrianmonk on Wednesday March 25, 2020 @07:29PM (#22689414)
Huh, I guess "hard not to call" could be interpreted as a disclaimer or qualifier meaning "I can't prove this, and it's only my opinion".

However, I interpreted it differently, to basically mean that because of objective fact, of all the explanations you can think of, only one of them is defensible. In other words, it's similar to saying "admit it, this is the only reasonable conclusion".

Re:Chrome phasing out support for User-Agent by sjruckle on Monday March 30, 2020 @05:16PM (#22732371)
The original post had the phrase "hard to not call" rather than "hard not to call".

The meaning is inverted by swapping the "to" and "not".

Re:Chrome phasing out support for User-Agent by MikusR on Wednesday March 25, 2020 @03:16PM (#22687583)
Re:Chrome phasing out support for User-Agent by Wowfunhappy on Thursday March 26, 2020 @10:57AM (#22694137)
As a semi-counter:

Slack, Skype, and Zoom video calls don't work in Firefox, even though WebRTC is an open standard. But Google Hangouts works perfectly.

I'm loath to give Google credit for something that ought to be standard practice, but of the major (key word) free video conferencing options, they seem to be the only one that's Firefox-compatible.

Re:Chrome phasing out support for User-Agent by iso1631 on Wednesday March 25, 2020 @02:12PM (#22687018)
I try out google products on occasion and find them rubbish compared with alternatives, so go back to non-google products.
Re:Chrome phasing out support for User-Agent by michaelmrose on Wednesday March 25, 2020 @03:12PM (#22687539)
Regarding google properties what do you prefer and why?
Re:Chrome phasing out support for User-Agent by iso1631 on Wednesday March 25, 2020 @03:20PM (#22687619)
Google maps does tend to be better than OSM when it comes to route finding, I use !gm when I want routing. On my phone I use apple maps though.

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 by michaelmrose on Wednesday March 25, 2020 @03:39PM (#22687778)
I prefer mu4e (mu for email) although ultimately I'm still using my gmail account just with another interface. I like the idea of ultimately just setting up a mail server but realistically its really really hard to switch everything at once when you have a lot of existing accounts so I'll probably be maintaining a gmail account forever.

I'm trying maps.me because unlike google it does offline walking directions but I haven't used it enough.

I really want to like duck duck go but it feels like google still provides better results.

Re:Chrome phasing out support for User-Agent by iso1631 on Thursday March 26, 2020 @08:30AM (#22692839)
> I really want to like duck duck go but it feels like google still provides better results.

I find I get better results with ddg than google. YMMV I guess.

Re:Chrome phasing out support for User-Agent by namibj on Thursday March 26, 2020 @01:07AM (#22690882)
I us brouter for my usecase of foot/bike nav in hilly terrain. Using OSM And for the UI.
Re:Chrome phasing out support for User-Agent by arendtio on Wednesday March 25, 2020 @03:11PM (#22687532)
In fact, just this week I thought about why Google doesn't make its mobile maps website fast again. It is such a pain to use it on older phones and I totally don't get, why it has to be that slow (doesn't matter if chrome or Firefox).