News for hackers. Stuff that matters.
Re:Google IO streaming live by spudlyo on Wednesday May 19, 2010 @12:36PM (#1361466)
Firefox and Opera on board as well. This seems like a big deal.
Re:Google IO streaming live by agotterer on Wednesday May 19, 2010 @12:39PM (#1361475)
How long will it take for Safari to switch away from their beloved h264? It usually takes Apple years to admit they lost a format war.
Re:Google IO streaming live by jws on Wednesday May 19, 2010 @01:30PM (#1361643)
Why would they switch to a poorly specified format that uses more CPU (battery), and delivers poorer video for the bit?

(See http://news.ycombinator.com/item?id=1361442)

How long until Google releases a real specification? (the current one is quite bad, it would be frightening to design silicon from blocks of uncommented C code lifted from the on2 implementation and foisted off as a specification. How long until someone writes an encoder that is incompatible with your silicon? Will it matter if it is your fault or theirs?)

How long until there are hardware VP8 decoders? (to save your battery)

How long until the patent holders decide to sue? (VP8 is extremely similar to H.264. They left out the most obvious IP in the algorithms, to their detriment, but only the patent owners know if they will sue. Though, I wonder if licensing the MPEG-LA properties covers VP8 decoders as well. If so, then Apple won't care, they already license.)

Re:Google IO streaming live by randallsquared on Wednesday May 19, 2010 @01:14PM (#1361593)
A long time. No one is going to stop serving up h264 if they already do; at best, this will only slow new adoptions. However, maybe I'm wrong; it would be interesting to see Youtube, et al do something to push on Apple... perhaps using h264 only for low resolutions or something. I don't think that anyone can afford to just cut off iPhone and iPad traffic by going flash-or-vp8 only.
Re:Google IO streaming live by stcredzero on Wednesday May 19, 2010 @01:55PM (#1361750)
Going low res on H264 would do it. Users would blame that on the device!