4 ms·
Honestly... I don't know if that's intentional; Drive 'files' get really laggy really quick in Chrome too.
by jfrunyon 6y ago
Honestly... I don't know if that's intentional; Drive 'files' get really laggy really quick in Chrome too.
- michaelt 6y agoThere are a lot of claims [1] that Google makes a ~suspicious number of accidental mistakes~ that harm performance on competing browsers. [1] https://www.zdnet.com/article/former-mozilla-exec-google-has-sabotaged-firefox-for-years/ https://www.zdnet.com/article/former-mozilla-exec-google-has...
- jfrunyon 6y agoI'm aware. However, Hanlon's razor suggests it's not intentional. Moreover, I think Occam's razor suggests the same: it's a lot simpler if we assume they just primarily test in their own browser (just like I'm sure Mozilla primarily uses Firefox) and just don't care enough to fix any performance deficiencies they do identify based on browser market share / amount they think users will care. (Keep in mind: I'm not saying Google is doing the right thing and trying to ensure an equal experience across browsers; I'm just saying I don't think they're intentionally trying to make their pages break other browsers)
- can16358p 6y agoDon't know, maybe not. It works flawless in mobile Safari, for example. Even though it's not intentional, I'm pretty much sure Google would be more inclined to say "hey use Chrome" instead of fixing it for Safari.