5 ms·
They just announced the open-sourcing of VP8 under a royalty-free licence :) http://www.webmproject.org http://www.webmproject.org
by nixme 16y ago
They just announced the open-sourcing of VP8 under a royalty-free licence :)
http://www.webmproject.org http://www.webmproject.org
- icey 16y agoSomeone has to talk to Google about their terrible naming practices. Between VP8 & V8, Go and Closure, I'm amazed any of us can remember what Google product is what.
- deleted 16y ago[deleted]
- milkshakes 16y agoPersonally, i think their "pairs" ( gin and guice, nacl and pepper) are both effective and cute. As for the ones you mentioned, v8 is a faster JavaScript engine , which makes sense (see http://en.wikipedia.org/wiki/V8_engine http://en.wikipedia.org/wiki/V8_engine ). Go is a language that is easy to get started with. Vp8, they inherited when they bought on2. I haven't used closure, and don't know much about it, but I'm guessing to those familiar with it, it makes sense. At very least, their names are much more intuitive than, for example, apache software names
- stuntmouse 16y agoFor an even better contrast, compare with Microsoft.
- spudlyo 16y agoFirefox and Opera on board as well. This seems like a big deal.
- agotterer 16y agoHow 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.
- randallsquared 16y agoA 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.
- stcredzero 16y agoGoing low res on H264 would do it. Users would blame that on the device!
- jws 16y agoWhy 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 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.)