6 ms·

Am I understanding this right? It didn't actually slow it down... it just didn't speed it up for those browsers when it added features to make it faster for Ch

• binarycrusader 8y ago
  From the fine article: "YouTube's Polymer redesign relies on the deprecated Shadow DOM v0 API only implemented in Chrome. You can restore YouTube's faster pre-Polymer design with this Firefox extension..."
• sp332 8y ago
  The new version uses new features which only Chrome has implemented. For IE it still serves the old version, but for FF and Edge, it serves the new version together with a compatibility layer that makes it slower. So they could have just served the old version, but they decided to serve a new, slow version instead.
• soapdog 8y ago
  The key point here is that they made it in a way that uses a deprecated API that will not be implemented anywhere else but in Chrome. Even Chrome own platform status page[1] says v0 is deprecated and scheduled for removal. By making their web properties rely on APIs which are no longer in standards tracks, they essentially harm the interoperability of the web. It is very comfortable when you control both extremes of some web property (the video sharing platform and the browser) to make sure they work well together and let the rest of the world play catch up. We have standards for a reason, so that things such as this are avoidable and you can use your browser of choice, whichever that browser is, on the web. By allowing their web developers to play the "chrome-first-and-foremost" game, they make the net-positive side-effect of acquiring more users for their browser, after all, who wants to use a slower browser right? [1]: https://www.chromestatus.com/feature/4507242028072960 https://www.chromestatus.com/feature/4507242028072960