Youtube has used vp8 since 2010. Openly licensed video codes were in use through the mid-2010s.
Youtube has used vp8 since 2010. Openly licensed video codes were in use through the mid-2010s.
In 2010 the majority of (YouTube and other) videos were still served as H.264, because no major browser supported it back then and the majority of video playback devices were already smartphones (without vp8 decoding capabilities)
iOS for example didn't support VP8 until iOS12 in 2019, Firefox and MS IE only added it in 2011. Even Google only added VP8 to Chrome in September 2010.
So the statement is correct IMO
I find this extremely difficult to believe. In 2010 the only widely used smartphone would have been the iPhone. The Motorola Droid was the first widely marketed Android device in the US and was only launched in late 2009.
No major browsers didn't support VP8 back then, and among the remaining devices (other appliances than PCs with those Browsers) the majority of video playback devices were already smartphones (not supporting VP8 in 2010).
Apologies for the lack of clarity.
It's why the h264ify extension existed, and forced h264 was for that time a large part of the reason Safari had vastly superior battery life.
Chrome didn't support VP8 until the first stable release in September 2010, others browsers added it in 2011.
They can be as aggressive as they want, when opening a video the client/server agreed on a codec both support and in 2010 that codec wasn't VP8
The context is that in mid-2010 the majority of the codecs used on the web were based on a closed licensing system, which is objectively true based on the provided information.
Your statement that Google enabled and enforced the codec prior to HW-decoding support is not wrong because of that, just your overall attitude on dealing with information is.
Reason: There was also no widespread VP8 HW-decoding support in 2011 and 2012 in most devices. Mobile chipsets vendors (Qualcomm, Samsung, TI,...) only added HW-decoding for VP8 from 2012 premium tier chipsets, so VP8 was SW-decoded on many devices in the market well into ~2014.
But in mid-2010 (!!) there was no Browser able to handle VP8 even in Software, and no meaningful embedded device supported the codec either