The problem still lies in patent issues/royalties. This is why there is a lack of developer support around H.264. It doesn't matter how much better it is technically if there is constantly this looming threat that it will cause legal problems down the road.
Sure you need browser support for this to happen. And I think H.264 has the best chance. Better quality currently. Has support from MS and Apple. 2 of thw biggest players in the industry. And Google will support both simply to ensure they are up to speed on who ever wins the war. So that leaves only Modzilla and Opera who currently do not support H.264. Yes Modzilla's Firefox has a large market share but I think they will be left behind if H.624 wins.
Apple is by no means one of the two largest players in the browser market. According to
NetMarketShare, Firefox has a market share 4.5 times that of Safari and Chrome's market share is almost 1.5 times that of Safari. If we use
StatCounter's info, Firefox's market share is more than 7 times that of Safari while Chrome's market share is more than 2.5 times that of Safari. The point I'm trying to get at with that info is that in terms of clout in the browser market, Apple doesn't have the same influence that Google and Mozilla do. Mozilla won't be supporting H.264 and Google is the one that introduced WebM so it would be unthinkable for them to drop WebM support. In fact, I'm sure it has precedence (if both a WebM and H.264 version are available, WebM would be used). I just tested this with a YouTube video (
here) - Chrome used the WebM version while Safari did not. Since both are available and Chrome gave precedence to the WebM version, it does in fact appear that Google is going to give precedence to WebM unless a web developer specifically codes their page so that H.264 takes precedence.
Sure WebM has more players supporting it. But the 3 biggest players (Apple, MS, Google) are supporting H.264. And really I don't think no matter what WebM is like. You can't win amy battle if all 3 of the big players are on the other side. (or on the fence as Google is now). The only way for WebM to win is for MS and Google to make WebM native to their browsers and remove the H.264 support. Pretty much screw Apple over as we all know H.264 is Apple's baby and they've been promoting that standard for ages now.
Again, WebM is native to Chrome much like it is to Firefox and Opera. Yes, Chrome and IE support H.264 but they also support WebM and thus, WebM has broader support than H.264. At this point, I'm pretty sure Apple is the only browser maker that doesn't support WebM in some fashion and with such a small market share, they don't really occupy a position with which they can push others into supporting H.264 exclusively.
So with Google on the fence and MS pretty much saying We like one but our browser with an add on can handle the other, the web professionals who would want an equal standard over all 3 big browsers. And cause of the big 3 Apple is the only one who is not on the fence, I think their vote for H.264 will be the winning one.
They may prefer H.264 right now but money speaks and to use H.264, you have to pay royalties (see
here). My argument is that the quality of WebM will likely reach that of H.264 well before any patent/royalty issues with H.264 go away. This means a lot for web developers - do you choose the absolutely free WebM or do you take the chance that MPEG-LA holds up their end of the bargain?
Market Share and Video Support (for reference):
- Internet Explorer - H.264, WebM (with codec installed; exclusive to IE9)
- Mozilla Firefox - Ogg, WebM (version 4.0)
- Chrome - Ogg, H.264, WebM (with version 6)
- Safari - H.264
- Opera - Ogg, WebM. H.264 (only on Linux and FreeBSD builds)
WebM - support in 4 of the 5
H.264 - support in 3 of the 5 (Opera does but not in their Mac builds)
72.99% of the market could theoretically support H.264 while 93.26% of the market could theoretically support H.264 using NetMarketShare's numbers.
EDIT: It appears that only commercial use of H.264 requires royalties. This doesn't detract from my point though - there are still royalty issues.