3 ms·

I'd be interested to hear what it was like on the dev team. I'm sure they don't super care about throwing elbows at Firefox now that that fight is won, so maybe

I'd be interested to hear what it was like on the dev team. I'm sure they don't super care about throwing elbows at Firefox now that that fight is won, so maybe the issues are just holdover from past decisions. But 10 years ago... was it just "don't test on firefox"? Or "heeey, we just made a brand new feature [that no one else uses] go ahead and use it in mail and maps!" Or more openly nefarious?

MSFT_Edging 3y ago
10 years ago, maps worked great on Firefox, I'd be genuinely surprised if they didn't test it there. I genuinely think they're doing anti-optimization for firefox users at this point. Edit: Did some google employee see this and turn a "maps on firefox load speed" knob? I decided to test again on a private window vs my typical plugin laden setup and it seems to be performing far faster than it has in years. wtf.
yjftsjthsd-h 3y ago
It's quite possible that they just try to optimize and only bother testing on chrome, so they're more or less passively conform to what Chrome is good at.