Mozilla exec says Google slowed YouTube down on non-Chrome browsers
cnet.com
cnet.com
This feels more or less like some premature dogfooding of Polymer. It probably would've been advisable to serve the old version until modern non-Chrome browsers caught up, but Shadow DOM v1 will be implemented eventually so my guess is they made the decision to transition those users now.
[0] https://www.polymer-project.org/
[1] https://www.polymer-project.org/3.0/docs/devguide/shadow-dom
How would you tell the difference?
- Because YT makes money on eyeballs and runs on every terrible device specific browser under the sun. Making users experience worse intentionally only really hurts them.
- Because we're in a forum of devs that are all about chasing the latest features and polyfilling everywhere that doesn't have them -- it's practically SOP. I totally believe performance problems like this wouldn't get caught in testing when everyone has a corp network connection and powerful laptops/workstations.
It is wrong to optimize for your own ecosystem, without optimizing for others?
Quite frankly, the company should be broken up forcibly by the government. All of these services should be profitable on their own, not used as loss leaders to grab as much ad data as possible and stamp out any sort of competition.
Oh! You could change user agents.
Okay, but without new features? Does the pre-polymer design served to IE maintain feature-parity with the shadow DOM (or its' polyfill equivalent)? Because YouTube never _seemed_ slow to me on FIrefox, but I'd hate to miss new features.
They've reached or passed maturity and are adding dubious features like the miniplayer that keeps playing the video you've just back-buttoned out of. Things that benefit advetisers, not users.
The truly beneficial features should be server-side; culling those awful 'Top 10 Shocking ...' videos from my recommendations, for example. Or realising that just because I watched one programme about military re-enactment, once in ten years, I probably don't want to watch another 30.
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?
But in this case I don't think they are at fault. As far as I understand it they didn't they just over-optimize for their own browser, which is not quite the same as degrade performance on other browsers on purpose.
Because that is what YouTube's frontend is currently running under the hood: Web Components and Shadow DOM. Both W3 standards. No magic at all.
Although it's true that only Safari and Chrome (through WebKit and Blink) currently have the best support for Web Components, and polyfills are required for everything else due to flaky support.
Google even mentions this in the Polymer README:
"Web Components are now implemented natively on Safari and Chrome (~70% of installed browsers), and run well on Firefox, Edge, and IE11 using polyfills. Read more below."