On Jan 12, 12:56 pm, Moandji Ezana <[email protected]> wrote: > On Wed, Jan 12, 2011 at 12:15 PM, Karsten Silz <[email protected]>wrote: > > > Daring Fireball has some good questions > > I guess Google would say that Android and Youtube are not Chrome...
Fair enough about Youtube, but isn't the Android browser called Chrome, too? > Any speculation as to the real reason for this? Merely resource allocation? I don't know how much work the H.264 decoder was for Google. If they bought it someplace else, the vendor is probably also doing the hardware acceleration on the various platforms for Google. If Google build it themselves, then they could save quite some effort there. Google bought on2 (owner of VP8/WebM) for 106 mio. and spent some more on open sourcing WebM, so they must have bigger plans here. I'm not smart enough to figure out what they are - H.264 as one of the required Blu-Ray codecs is too entrenched in movies and TV to be completely displaced and none of Google enemies (in order of importance: Facebook, Apple, Microsoft) would be hit hard. Yes, iOS device dont' decode WebM in hardware - but neither does anybody else's devices. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
