Of course, region-specific copyright deals are incredibly complex etc. etc., so I could imagine it was just a matter of waiting out until the last person putting up a veto retired or moved on to other things.
Of course, region-specific copyright deals are incredibly complex etc. etc., so I could imagine it was just a matter of waiting out until the last person putting up a veto retired or moved on to other things.
Judging from the clunky, buggy, nonsensical experiences on 2nd tier streaming services (i.e., everything except Netflix, Amazon Prime, YouTube, Disney+, Max), I'd say the biggest cost is probably hiring a decent Engineering+Product+Test team. There are complexities here, like making these things work on different TV brands, versions, older models, etc.
Pushing all the complexity to YT seems like a total no-brainer.
With the exception of Netflix, these other companies' apps are similarly buggy and painful to use. I run into an at least issue daily (usually multiple times a day) in every streaming app I use except Netflix.
Not sure where this come from, I have been unsubscribed for a few months so my experience is not current but back in mid 2024 I got video not showing up with some obscure error codes once in a while.
It is a bit better now.
I think part of the problem is their dumb microservices architecture. They operate something like 10,000 microservices and different devices talk to different subsets of those.
On our old, cheap roku stick, they regularly would produce “could not stream” errors or fallback to screenshots instead of trailers (which was actually better!) more often than not. The website would be fine, and no one else I know noticed the outages.
The worst thing is that I’ve worked at places that have moron middle managers that actually decided to emulate this and moved to microservices. It wasted years of my life at work.