4 ms·
> Except that it further entrenches Flash in the short to medium term, possibly longer. Only because Microsoft and Apple choose not to support WebM. Prior to
by jasonlotito 16y ago
> Except that it further entrenches Flash in the short to medium term, possibly longer.
Only because Microsoft and Apple choose not to support WebM. Prior to Google's choice, Firefox (with rather significant browser usage stats) wasn't supporting H.264 either, which kept Flash on the web. Also, people keep referring to IE, but it still needs Flash. Sure, IE9 is coming, but we'll see what the adoption rates will be like.
Point is, Google throwing out H.264 didn't change the short or medium landscape much.
> Everyone points to the GIF fiasco. The net result? PNG was born.
You completely miss the point. GIF is a lesson, and we should learn from it. More importantly, PNG wasn't adopted over night. You can't just flip a switch and make everything alright.
> If the screws are ever put to us on H.264, you'll see exactly the same thing, only quicker.
Or, you can avoid the entire problem, put effort into free formats now. Don't repeat past mistakes.
> The elephant in the room here is that the fundamental problem is software patents. They need to be completely abolished.
Yes. Supporting them doesn't help matters.
- masklinn 16y ago> Only because Microsoft and Apple choose not to support WebM. When they made their choice WebM wasn't an option because it didn't even exist yet. Microsoft might be a different issue, but Apple has now shipped almost 150M devices with hardware h.264 support and no webm support at all. > You completely miss the point. GIF is a lesson, and we should learn from it. GIF is completely irrelevant to the issue at hand (or, if you want to reach for it, WebM is actually more at risk of a GIF-type scenario than h.264)
- jasonlotito 16y ago> When they made their choice WebM wasn't an option because it didn't even exist yet. IE9 is still in development. They can still choose to support WebM. Apple could still choose to WebM support. The point isn't that Apple and Microsoft can choose. Rather, you can't expect to ask Google to support H.264 and not ask Microsoft and Apple to support WebM. Apple and Microsoft don't want to support it. Fine. Google doesn't want to support it. Fine. Neither H.264 and WebM are written into the standard. Fine. Let the competition begin. The best technology that meets all the needs of the various groups will win. > GIF is completely irrelevant to the issue at hand (or, if you want to reach for it, WebM is actually more at risk of a GIF-type scenario than h.264) No, and no. I'd explain more, but I can't follow your logic. (Nor do I really want to try. Sorry, but you seem far too emotional about the topic. I'm probably wrong, but your comment comes off that way).
- spiffworks 16y ago> Apple could still choose to WebM support. In fact, Imagination Technologies, the people who make the GPUs for the iPhone(and the iPad as well, I think), have already announced full vp8 support in their next-gen hardware decoders, so it would be really easy for Apple to include webm support in the next iPhone or the one after that. And they're safe from any patent threats as well, since they're already MPEG-LA licensees. It will be interesting to see if they do.
- morganw 16y ago> it would be really easy for Apple to include webm support And Matroska support. Building container parsers that are resilient to fuzzing attacks is non-trivial. Can I assume you'd like trick play (ffw, rew, scrub), too?
- kinetik 16y agoContainer parsing: it's not that hard. Besides which, they can use one of the freely licensed existing parsers to solve that problem. Trick play is already implemented. If you have to do major rework of that area to support a new format, you're doing it wrong.
- commandar 16y ago>IE9 is still in development. They can still choose to support WebM. I was talking with a friend yesterday and mentioned how hilarious it'd be if Microsoft decided to adopt WebM on WP7 and then attack Apple for being too closed. :)
- jasonlotito 16y agoI love the people shouting to the roof for standards support and how H.264 is a proper standard and how we should support it because it's being used everywhere. I just can't help think of the OOXML debacle.
- 16y ago
- sudont 16y ago> WebM wasn't an option because it didn't even exist yet. And when WebMx is released, everybody will hound those who don't immediately change their product strategy to fit this. This is also a good reason for why Apple isn't using WebM: it's not a standard, it's as controlled by Google as Flash is controlled by Adobe. They're essentially giving a bunch of control of their device to an outside company.
- spiffworks 16y agoThe webm spec is frozen, and all patents are irrevocably licensed. Webm is not 'controlled' by Google.
- sudont 16y agoThe patent thing is just FUD by Apple proponents. But, I won't support WebM until it's an ISO standard, frozen is just a promise at this point. Their own site says "dedicated to developing a high-quality..." which, taken literally, means that the project is still underway. Also listed on the front page: "Submit patches and improvements" Yet again, saying that it's a work in progress.
- ZeroGravitas 16y agoThe encoder is being improved, and the decoder is being optimised for speed on various platforms but the spec defines what the decoder does and it was effectively frozen as soon as Google converted a bunch of Youtube videos and got hardware manufacturers on board. Any change to the format would break existing content (most of Youtube) and shipping hardware.
- bryanlarsen 16y agoThe fact that the standard is frozen is not incompatible with them improving their implementation.
- ootachi 16y agoISO leads something to be desired: witness the glacial pace of C++0x (now C++1x). I'd prefer some standardization of VP8 - don't get me wrong - but going through ISO would likely be a mistake.