4 ms·

It seems to me that Google is always trying to make their products run much slower on browsers that aren't Chrome.

cratermoon 6y ago
It's unlikely they put any effort into intentionally make them run slower, it's just that they are written to work optimally on Chrome and minor differences in the behavior of things like the V8 vs. SpiderMonkey and Blink vs Gecko. Given that each one is written with different tradeoffs, it's not surprising things perform differently. Whether or not the Google programmers use specific proprietary knowledge about the behavior of Chrome to optimize performance is different. If they do, that would be similar to the things that got Microsoft in trouble.
- clankyclanker 6y ago
  I'd agree with you, except for Google's long and sordid history of doing exactly that, time and time again (found with a 30-second search): https://tech.co/news/google-slowed-youtube-firefox-edge-2019-04 https://tech.co/news/google-slowed-youtube-firefox-edge-2019... https://www.techspot.com/news/79672-google-accused-sabotaging-firefox-again.html https://www.techspot.com/news/79672-google-accused-sabotagin... https://www.zdnet.com/article/former-mozilla-exec-google-has-sabotaged-firefox-for-years/ https://www.zdnet.com/article/former-mozilla-exec-google-has... Google knows that every time they release a Firefox bug, FF's user percentage goes down a tiny bit. Repeat over dozens of bugs, for years, and you have a strategy. There's one blog post from another Mozillian that I can't find anywhere that came out within the last year with other examples, I think it was on HN.
  - ficklepickle 6y ago
    I read that post. It was enough to convince me of malice at the time. I don't have the link though.
  - bscphil 6y ago
    > There's one blog post from another Mozillian that I can't find anywhere You are looking for https://web.archive.org/web/20180728122724if_/https://twitter.com/cpeterso/status/1021626510296285185 https://web.archive.org/web/20180728122724if_/https://twitte...

It's unlikely they put any effort into intentionally make them run slower, it's just that they are written to work optimally on Chrome and minor differences in the behavior of things like the V8 vs. SpiderMonkey and Blink vs Gecko. Given that each one is written with different tradeoffs, it's not surprising things perform differently. Whether or not the Google programmers use specific proprietary knowledge about the behavior of Chrome to optimize performance is different. If they do, that would be similar to the things that got Microsoft in trouble.

clankyclanker 6y ago
I'd agree with you, except for Google's long and sordid history of doing exactly that, time and time again (found with a 30-second search): https://tech.co/news/google-slowed-youtube-firefox-edge-2019-04 https://tech.co/news/google-slowed-youtube-firefox-edge-2019... https://www.techspot.com/news/79672-google-accused-sabotaging-firefox-again.html https://www.techspot.com/news/79672-google-accused-sabotagin... https://www.zdnet.com/article/former-mozilla-exec-google-has-sabotaged-firefox-for-years/ https://www.zdnet.com/article/former-mozilla-exec-google-has... Google knows that every time they release a Firefox bug, FF's user percentage goes down a tiny bit. Repeat over dozens of bugs, for years, and you have a strategy. There's one blog post from another Mozillian that I can't find anywhere that came out within the last year with other examples, I think it was on HN.
- ficklepickle 6y ago
  I read that post. It was enough to convince me of malice at the time. I don't have the link though.
- bscphil 6y ago
  > There's one blog post from another Mozillian that I can't find anywhere You are looking for https://web.archive.org/web/20180728122724if_/https://twitter.com/cpeterso/status/1021626510296285185 https://web.archive.org/web/20180728122724if_/https://twitte...