Obviously getting Microsoft to add codec support is another issue altogether, but it seems plausible that it could be done. Since Google would own all of the IP, they can sign some patent contract with Microsoft promising that yes, this really is open, and no, they won't ever sue Microsoft over implementing the standard. If that were the case it would make the VP8 codec the most promising among the alternatives for Microsoft, since it would be free and its IP status would be certain and guaranteed. It seems like the question hinges on whether or not Microsoft plans to add <video> support at all, and since they've made vague claims supporting HTML5 and these new fangled web standards, it seems plausible that some version of Internet Explorer could support the codec in the future (even if it takes them a while).
Giving up on the car metaphor, it's Flash support for H.264 that makes it viable for 85% of the market. Adobe can win it for VP8 if they want to, but I think Google can do it with out them too, it'll just take longer.
I'm not sure Google ever actually stated on-the-record why they refused to add Theora support to YouTube, but 'cost to re-encode all that video' has been widely cited, and I don't see why re-encoding with VP8 would be particularly cheaper than re-encoding with Theora.
Flash never supported Theora, which invalidates its use for the vast majority of web users today. Even with HTML5 video, content protection worries is going to keep a lot of content wrapped up in Flash players for a while. On the other hand, Flash has a good chance to support VP8--Adobe already holds a license option on VP7 and has supported the codec line in their players.
The lack of players, content hosts, and embedded decoders all prevented Theora from ever taking off. I think there's a better chance that Google's direct backing of a codec (both as a content host, mobile platform, and browser, give VP8 a better shot.
I have also read that Theora's "patent-free" status is questionable; to my knowledge nobody has reviewed the codebase to ascertain what patents it may infringe on. On2, as a commercial enterprise licensing its codecs to others, has had to navigate the patent minefield already. I trust its status more, especially with Google behind it.
As for what Firefox will do, well, that remains to be seen. I just think it makes sense for VP8 to succeed where Theora failed.
I didn't know that Adobe had an option on VP7, but I'd be impressed if Adobe added VP8 support to Flash - I mean, the whole point of this exercise is to undermine Flash, and I'd be surprised if Adobe joined in except in the face of overwhelming customer demand.
Yes - if Google officially supports VP8 in Chrome, Android and YouTube, that'll be a very strong argument (far stronger than Theora has had) for other content providers and user-agents to support it... but Apple/Nokia/MS and YouTube already support h264, so adding support for another, less efficient codec seems silly.
Theora's "patent-free" status comes entirely from On2 saying "we give everybody the right to use all our IP involved in VP3". Presumably On2 had the same due-diligence issues when it was licensing VP3 to others; I don't see how On2 could give VP8 a stronger "patent-free" declaration than Theora already has, unless (as other people have suggested) Google has bankrolled an exhaustive search for applicable patents.
I don't really mind whether VP8 or Theora winds up being the dominant format on the web, I'm just skeptical that VP8 is all that different when it comes to the pain-points that have prevented people from adopting Theora.
Eg: http://www.digital-digest.com/news-61385-On2-Video-Codec-VS-...
Oops, that should read: On2's main claim to fame for VP8
There's an interesting post about the problems with VP8 posted by an x264 developer here: http://x264dev.multimedia.cx/?p=292
Considering he's an x264 developer that article is very positive about the quality of the VP codecs. The stuff he's down on e.g. it being proprietary, licence fees, patents, big name corporate approval, mobile support, buggy encoder are all stuff people expect Google to fix quite easily (well apart from patents).
It will benefit Google in two ways:
First, it insulates them from encoder licensing fees going forward, and from decoder license fees if MPEG-LA decides to back off their free-for-web-streaming arrangement. It also means they're free to bundle the codec with Chrome.
Second, if you believe the publishing hype, it could save them up to 50% bandwidth. I doubt it's that effective, but at Youtube's scale, processing is cheap and bandwidth is expensive; every 1% helps. If they can reduce the number of storage nodes, bytes transferred, and by extension, open conns/sec, that translates to very real savings.
(I'm quite certain I'm wrong on this point, but I'm interested in learning why)
Eg, take a frame which has a solid chunk of blue. Codec 1 removes some of data to make things more consistent and then compresses it. Codec 2 looks at the output of codec 1, sees the consistently large blue area, doesn't see any info worth removing, and compresses it.
Unfortunately for that cunning plan, Google clearly sees more benefit from a codec that's compatible with the open web and open source than they do from licence discounts.
Sweet.