3 ms·
Even better, given that the issues raised by (iirc) Mircosoft and Apple against webp becoming the HTML5 standard video codec (and thus mandatory to support for
by gillianseed 14y ago
Even better, given that the issues raised by (iirc) Mircosoft and Apple against webp becoming the HTML5 standard video codec (and thus mandatory to support for HTML5 compliance) was that of 'patent uncertainty', with this agreement we can finally get a really great royalty free standard codec which can be used with any browser which is HTML5 compliant.
Same goes for WebRTC, which should now be on the fasttrack to be accepted as the standard for RTC (currently supported by Chrome, Mozilla and Opera).
I think having open and royalty free standards for such integral parts of what is likely to be the 'future of the web' is extremely important to foster innovation, thanks to VP8/VP9 and Opus we now have technically competitive offerings which anyone can implement free of charge across all platforms and for whatever interesting solutions they can come up with.
- snogglethorpe 14y ago> the issues raised by (iirc) Mircosoft and Apple against webp becoming the HTML5 standard video codec "webm" is the video format (and uses VP8). "webp" is a related image format. [webp is not very compelling as an image format on its own, but maybe the relationship with webm confers some advantage...]
- gillianseed 14y agoyes, that was a spelling error, but given the context of the discussion (standard video codec) I doubt anyone failed to understand that I meant webm.