Yes, war's won
No, heating up
Steven J. Vaughan-Nichols
Best Argument: No, heating up
Audience Favored: No, heating up (63%)
Video wars...who cares?Chris Dawson: Web video wars? Does anyone besides the web video teams at Google, Apple, and Microsoft actually care? HTML5 already supports the majority of competing codecs across most browsers. Sure, Google continues to posture with WebM, Apple is the poster child for vendor lock-in, and Microsoft continues to struggle for relevance on the Web; Mozilla is just trying to figure out who to follow.
I don’t lay awake at night wondering which standard I should use to encode the videos I produce (and I produce a lot of them). The HTML5 tag solves a whole lot of problems by letting web browsers display whatever they support. 8-core processors solve even more by making multiple renderings of web videos in different formats trivial.
In the end, multiple codecs will grumpily coexist, made largely into religious issues for developers by HTML5, and, as long as they can watch YouTube and Netflix, ignored by users.
Flash, as alive as everSteven J. Vaughan-Nichols: Yes, we all hate Flash. Even Adobe's not that crazy about it anymore. Too bad. There's still no replacement for it.
HTML5 video you say? What about it?
HTML5's video tag doesn't define which file format, such as MPEG4 or WebM, or video or audio codec, such as H.264 or VP8, are permitted. All HTML5 does is let Web developers set up case statements so that they can supply a choice of various combinations of containers and codecs in the hope that your device can support one of them.
In other words, HTML5 video is just a rug that covers the dirt of multiple video formats. It doesn't replace Flash at all. In fact, you can still use Flash within it. We're a long way from being Flash free.