Huh? IE6 is a browser not a standard.
Well, neither can H.264 be a standard, it is a non-free codec for video. The key was de facto..
Internet Explorer 6, at the peak of its dominance, became the standard that many web developers developed for. Even though it wasn't a standard, when it had over 90% of the market, it was often the only browser that was developed for and other browsers were locked out or suffered. Browsers like Opera spoofed as IE by default, Netscape had quirks to behave similar to IE in some respects...
It's saying that everyone who wasn't on H.264 would suffer or be forced to conform, as was the case with IE6 for some time.
Let's not split hairs. Browser != data format.
I can see the point you're arguing (or at least what the author is trying to argue, whether or not it's your opinion as well). But it's at best a stretch.
In the IE6 "glory" days, it wasn't just a case that Websites wouldn't be made to work for other browsers (meaning they were never tested or, if they were, it was beyond scope to fix). It was worse than that. Sites would deliberately look at the user agent and simply not work if it was a non-IE browser. This still happens. I still come across sites that not only warn you they're optimized for IE and FF (ie proceed at your own "risk" when using Chrome). Some go further and simply won't work if you try and use Chrome. It's thankfully rare but it still happens.
Anyway, the point here is the IE6 displayed HTML/CSS content differently than other browsers and had JS differences too. It took effort to make things cross-browser and it was (and arguably still is) a big deal.
So the stretch of comparing H.264 to IE6 is twofold:
1. We're talking about the entire Web vs the narrow context of Web-based videol so it's a question of scope; and
2. Converting video from one format to another can be automated. Converting a site designed for IE6 to work on other browsers cannot.
So not only aren't the problems analogous but the author is engaging in scaremongering to try and equate H.264 with the (stipulated) horrors of IE6.
Sure it can. You run it through IE6 and print to an image format of your choice.
>1. We're talking about the entire Web vs the narrow context of Web-based videol so it's a question of scope; and
Yes, and thanks to the narrower scope it's not as big a deal to convert between video formats, but there's still going to be a marked loss of quality.
>So not only aren't the problems analogous but the author is engaging in scaremongering to try and equate H.264 with the (stipulated) horrors of IE6.
Viewing a website designed specifically for IE6 is likely to cause similar loss of fidelity to viewing a video transcoded from VP8 to H.264, or vice versa.
>Let's not split hairs. Browser != data format.
The data format in question is the HTML accepted by IE6. That data format actually works fairly well with modern web browsers, much like VP8 decoders will likely be bundled with H.264 encoders once the patents run out and H.264 can properly be called an open standard.
The word "standard" doesn't mean what you seem to think it means.
(I wish standards were free -- I've always wanted my very own copy of IEC 60908.)
Look up "de facto standard" please.
"Works on IE6" is a type of HTML/CSS/JS that works on IE6. People had to make websites to work on IE6. That meant new features of the web (HTML, JS & CSS) could not be used because they didn't work on IE6.
If you don't understand why the article is correct, you really don't understand the topic. It's fine to disagree, but this statement demonstrates your complete lack of knowledge in the area.
Personally I think "bait and switch" fits here correctly.
> > But it would become another closed de facto standard, just like IE6. > Huh? IE6 is a browser not a standard.
I don't think that you understand what "de facto standard" means. Or maybe you understand, but choose to ignore it to make bullshit argument.
> > This is comparing apples and oranges. Flash is a plugin, > This is splitting hairs and a straw man.
Really? I thought we are talking here about video codecs not Flash. Please stick to meritum. Dont use red herring. Why do you insist to bring Flash to discussion about two video codecs?
>WRONG. Bizarrely wrong in fact since we're arguing about the HTML5 container for video and supported codecs. Flash isn't involved.
Oh so now you insist that Flash isn't involved in this discussion?
> This isn't vapourware either. Modern browsers already support it.
But old browser are still here for at least couple years. I still have to deal with people using IE6 - 10 years after original release. One of the ways, for people building websites, to deal with old browser is to use Flash for certain tasks. So some websites still require Flash as they need to deal with this type of users. But let's not divert this discussion to Flash as it's NOT what we are talking about.
> If there are two dominant standards, sites will be faced with a choice: double-encode everything or pick one. Many have already picked H.264. What's more likely? Double-encoding or simply delivering H.264 to Chrome via a Flash (rather than HTML5) container?
True, there will be probably double encoding involved, but most likely only for certain period of time, the time of transition. Once WebM will gain popularity, double encoding will end, as majority of providers will chose free format. And google just took first steps to popularize WebM.
> If anything, this move prolongs the existence of Flash.
Here we go again. You bring Flash to discussion whenever you don't have another argument. But if you insist - there is still massive hole in your logic: "> What's more likely? Double-encoding or simply delivering H.264 to Chrome via a Flash (rather than HTML5) container?" I don't know if you realize but major players (youtube, vimeo, etc.) in web video double-encode at least since a year - at least to VP6 and h.264. But there is even bigger hole in your logic: "...simply delivering H.264 to Chrome via a Flash..." - you just contradicted yourself by saying that it's in fact h.264 that keeps Flash alive (that you hate so much). If we remove h.264 and propagate WebM, we will remove flash as a fallback dependency.
> > Just because a format is widespread offline does not mean that it is suitable for use on the web.
> Is the author really suggesting H.264 a) isn't widespread on the Web and/or b) isn't suitable for use on the Web? Really?
a) No, not really. You're putting YOUR words in original author's mouth. He said that it's widespread offline. He didn't said anything about it's web share. Your biased point of view implied this. b) Yes, he meant that, but you skipped context of the article. Article is in context of OPEN web, and in that context H.264 isn't suitable.
> If the author thinks this move will displace H.264 they are sadly mistaken. For one, the license fees for using H.264 are negligible for the largest players.
License fees for large players might be negligible but if another - free - format will become widespread enough they will simply switch to that free one, as there will be no reason to pay that fees. And as most big players are public companies, or parts of public companies, they have obligation to shareholders to maximize profits which is easy if you can cut costs.
> For another, there is an enormous installed base of devices with hardware H.264 decoding. Hundreds of millions in fact, most notably the various Apple iDevices.
And that step by Google is an attempt to change it. And given time it will change. First new devices will incorporate hardware encoding of WebM along with h.264. Later, given time they will abandon h.264. You think in categories of months. Big players think in years. Also, I remember people using similar argument against Android, and now android sells biggest number of smartphones.
> These provide a compelling use for the continued use of H.264 in the long term.
And to force world to use paid format for long term.
> Yes but double the processing and double the storage are real issues.
But adoption of WebM will not change situation. We encode to multiple formats whether WebM is here or not. And long term view is that widespread adoption of WebM might actually end that and end licensing fees. So double savings.
> What benefits are those exactly? At least for now the user experience, HTML5 video is still playing catch up to Flash video in terms of user experience.
So now you're arguing that there are no benefits of html5 video? What about the benefit of knowing that user of certain browser definitely have support for your video without requirement of using plugins, which might or might not be there? Honestly, are you trying that hard to shoot yourself in the foot, or are you just picking arguments when they are suitable to prove your point, whatever it is.
> HTML5 video is still playing catch up to Flash video in terms of user experience.
Are you now in favor of using flash instead html5 video? Sure html5 video is playing catch up with flash, but it's playing catchup regardless we use h.264 or WebM. And again, given time html5 video might catch up. If it will not than we will still use flash regardless if dominant codec will be h.264 or WebM.
> Worst case for IE is still about ~50%. That still makes it the single largest browser.
According to these stats http://en.wikipedia.org/wiki/Usage_share_of_web_browsers IE is loosing 10% of market a year. So it won't take much longer.
> I can't imagine it [Safari] getting WebM support anytime soon.
Apple might change their mind anytime if there will be money or pressure involved. Just like they finally removed ban on flash apps from appstore.
> By definition, not giving someone a choice takes away choices.
But you will have a choice. If you like h.264 you can install plugin, if you like Flash you will have Flash, and if you like WebM you will have WebM.
> All of the arguments for this move seem to be focused on the long term. That's fine but in the short term it will unarguably cause users and sites headaches.
Ah, sorry, I see you actually understand that it's not overnight change that they play in here. Sorry again your opinions above were worded (or understood by me) like you didn't understand that.
> That's fine but in the short term it will unarguably cause users and sites headaches.
That's true, but we are already in times of transition from Flash to html5 video, so that's the best time to make strategic moves like that.
> At best, the author's argument descends to "two wrongs make a right". > Note: I'm saying arguing in favour of Flash. In fact, I consider the lack of Flash on my iDevices to be a feature rather than a limitation.
I don't really understand what you are trying to imply here.
> Ironically this moves will likely prolong Flash and slow the adoption of HTML5 as a result.
As I stated many times above I don't think you're right about that. In fact I think opposite - keeping h.264 is prolonging flash and slowing adoption of HTML5.
> It's called bait and switch.
Not really. If anything, it's the eventual use of market power for profiteering.
> But it would become another closed de facto standard, just like IE6.
Huh? IE6 is a browser not a standard.
> This is comparing apples and oranges. Flash is a plugin,
This is splitting hairs and a straw man. The user does not care or typically doesn't differentiate between something that's part of the browser and something that is a bundled plug-in. The user experience is basically the same.
So any argument using a criteria about building in a proprietary and closed standard to the browser versus bundling a proprietary and closed plug-in is at somewhere between fatuous and disingenuous.
> If you want to do any kind of video on the web, you don't have a choice. Flash is needed.
WRONG. Bizarrely wrong in fact since we're arguing about the HTML5 container for video and supported codecs. Flash isn't involved. This isn't vapourware either. Modern browsers already support it.
> it is much more likely that an open format will prevail in the end.
If there are two dominant standards, sites will be faced with a choice: double-encode everything or pick one. Many have already picked H.264. What's more likely? Double-encoding or simply delivering H.264 to Chrome via a Flash (rather than HTML5) container?
If anything, this move prolongs the existence of Flash.
> Just because a format is widespread offline does not mean that it is suitable for use on the web.
Is the author really suggesting H.264 a) isn't widespread on the Web and/or b) isn't suitable for use on the Web? Really?
> In other words: The processing will always be there, and instead of re-processing to a slightly more compressed H.264 file for online play, it can be converted to an open format.
If the author thinks this move will displace H.264 they are sadly mistaken. For one, the license fees for using H.264 are negligible for the largest players. For another, there is an enormous installed base of devices with hardware H.264 decoding. Hundreds of millions in fact, most notably the various Apple iDevices.
These provide a compelling use for the continued use of H.264 in the long term.
> As already explained, videos are typically re-encoded or processed in some way anyway.
Yes but double the processing and double the storage are real issues.
> Notice the word "plugin". It means that we're basically removing HTML5 video, and returning to plugins. All the benefits of native video disappear just like that
What benefits are those exactly? At least for now the user experience, HTML5 video is still playing catch up to Flash video in terms of user experience.
> If I am not mistaken, the share of open standards based browsers is growing at the expense of Internet Explorer.
Worst case for IE is still about ~50%. That still makes it the single largest browser. Chrome's share exceeds Safari's (AFAIK) but the latter is still significant and I can't imagine it getting WebM support anytime soon. Apple are very much wedded to H.264 support by virtue of their devices if nothing else (anecdote: I played 6 hours of video on a plane on my iPad using 10% of the battery).
> it is H.264 which takes away choice.
By definition, not giving someone a choice takes away choices.
All of the arguments for this move seem to be focused on the long term. That's fine but in the short term it will unarguably cause users and sites headaches.
> I also find it puzzling that Google is being accused of giving users fewer choices, while Microsoft and Apple aren't even mentioned.
Hold yourself to a higher standard (and, more importantly, preach those standards to others) and you will be the recipient of greater scrutiny.
At best, the author's argument descends to "two wrongs make a right".
Note: I'm saying arguing in favour of Flash. In fact, I consider the lack of Flash on my iDevices to be a feature rather than a limitation.
Ironically this moves will likely prolong Flash and slow the adoption of HTML5 as a result.