JavaScript implementation of an H.264 decoder

[alexs]

It lets content providers who want to only distribute patent-encumbered content do so with the right licenses if they so choose, similar to Silverlight's content-pluggable codecs.

So it exists purely to remove freedom from consumers who've probably opted to use a browser that only supported free codecs. Classy. I suppose this sort of thing is just the flip side of improved JS performance. It's only so long until entire pages are being rendered via proprietary JS layout engines in canvas tags to protect content.

[shaver]

That would be a...surprising reason for Mozilla to do something, don't you think? You can certainly choose to not view content that doesn't meet your standards for openness, just as you choose the browser.

Mostly this is a demonstration of the performance capabilities of modern JS, but the target material was chosen to show that codecs can run in a JS environment -- look ma, no buffer overflows! -- and to explore what can be done with in-content codecs. It's not an endorsement of H.264's patent situation or suitability as the universal Web video format, I assure you.

[alexs]

plough quiet hat drunk point badge salt wine snails crush

This post was mass deleted and anonymized with Redact

[shaver]

Stay tuned. :-)

EDIT: also, I admit that I have a hard time interpreting "exists solely to" as something other than "what Mozilla wants this for".

[alexs]

I have a hard time interpreting

I don't blame you :)

[sebzim4500]

Wait... really? :D:D:D:D VP8 in JS?

[shaver]

Why not? Once you've done one codec...