3 ms·

>What on earth do you mean by "hijacked"? You're right, that was a poor choice of words. I meant dominated. >Mozilla and Google who are the ones trying to mak

>What on earth do you mean by "hijacked"? You're right, that was a poor choice of words. I meant dominated. >Mozilla and Google who are the ones trying to make browsers, not me. The point is that you shouldn't have to pay royalties to someone to ship a competitive browser which has support for the most widely used codec. Think of Rockmelt or Flock. If they had to pay millions to stay competitive, isn't that a net loss for the internet? >Also, I take issue with your saying "fully compliant". You're right again, I meant a competitive browser. >If anything, the fact that the spec is codec-agnostic suggests that the most "spiritually" compliant position would be for the implementation to be, as well I don't understand exactly what you mean here. I thought the whole point of HTML5 was that video becomes a first class citizen, so if I had to install a plugin for each codec, wouldn't that defeat the whole purpose? Or are you saying that every browser should include support for the widest range of codecs that it possibly can? I think its unfair to ask a non-profit organisation like Mozilla to license a codec for many millions of dollars. Could you elaborate?

GHFigs 16y ago
Or are you saying that every browser should include support for the widest range of codecs that it possibly can? No. Quite the opposite, actually. I am saying that a reasonable approach would have been for the browsers to defer support to the operating system. Apple does this. Microsoft does this. Mozilla, Google, and Opera have instead chosen to limit support to only the codecs they implement in-browser. (I say "would have been" because there's practically zero chance of this happening now.) One effect of this is that even on a system with h.264 already present you can't view it in those browsers. This is not a requirement of the HTML5 spec, an h.264 licensing issue or a technically intractable problem, but a choice made by those browser vendors to favor certain codecs. The point is that while the debate is frequently framed as a standards issue it's really more about the ideology of implementing things on top of those standards.

GHFigs 16y ago

Or are you saying that every browser should include support for the widest range of codecs that it possibly can? No. Quite the opposite, actually. I am saying that a reasonable approach would have been for the browsers to defer support to the operating system. Apple does this. Microsoft does this. Mozilla, Google, and Opera have instead chosen to limit support to only the codecs they implement in-browser. (I say "would have been" because there's practically zero chance of this happening now.) One effect of this is that even on a system with h.264 already present you can't view it in those browsers. This is not a requirement of the HTML5 spec, an h.264 licensing issue or a technically intractable problem, but a choice made by those browser vendors to favor certain codecs. The point is that while the debate is frequently framed as a standards issue it's really more about the ideology of implementing things on top of those standards.