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 s

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