4 ms·
> How would this explode in your face, exactly? What was the risk here? for one thing that actually happened because they did (and got away) with this: youtube
by gcbw2 7y ago
> How would this explode in your face, exactly? What was the risk here?
for one thing that actually happened because they did (and got away) with this: youtube engineers feel like they can leverage their site to dictate what they want in the browser space, by deliberately making it 5x slower on firefox and edge[0].
As a rule of thumb, if something looks fishy and shady, but just because it doesn't directly explodes in your face, treat it as a "but I don't have anything to hide" situation, and be against it. Because eventually, it will be your face.
[0] http://fortune.com/2018/07/25/youtube-slow-mozilla-firefox-chrome/ http://fortune.com/2018/07/25/youtube-slow-mozilla-firefox-c...
- darawk 7y ago> for one thing that actually happened because they did (and got away) with this: youtube engineers feel like they can leverage their site to dictate what they want in the browser space, by deliberately making it 5x slower on firefox and edge[0]. There's no evidence that that was deliberate. These two things are also pretty completely unrelated.
- fjsolwmv 7y agoThey deliberately chose to run pre-release performance testing on chrome but not other browsers.