Google To Push WebM With IE9, Safari Plugins 413
surveyork writes with this "new chapter in the browser wars: 'Google in a defense of its decision to pull H.264 from Chrome's HTML5 revealed that it will put out WebM plugins for Internet Explorer 9 and Safari. Expecting no official support from Apple or Microsoft, Google plans to develop extensions that would load its self-owned video codec. No timetable was given.' So Google gets started with their plan for world-wide WebM domination. They'll provide WebM plugins for the browsers of the H.264-only league, so in practice, all major browsers will have WebM support — one way or the other. Machiavellian move?"
Start your betting (Score:2, Interesting)
Something tells me that MS and Apple (and especially, Apple) will do all they can to break the plugin's functionality.
Re:Then has anyone decided to fork the H.264 build (Score:2, Interesting)
MPEG-LA isn't meant primarily to generate a profit, it's a collaboration of many patent holders who have pooled their patents to create a legal, high quality, open, widely supported video codec that they can all use, preventing a slew of inferior, proprietary incompatible video formats from each company. MPEG-LA, and their members, primarily want a codec that can be more or less used universally. It's not in their best interest to become "patent trolls" and sue people not making money off of their patents.
On the other hand, it's very much in their interest to sue large companies that are deliberately pissing in their pool, like Google.
As a consumer, H.264 is pretty much perfect. It essentially comes free with everything I own, costs me nothing to use on the web, is universally supported, and runs smoothly and sips power on all my devices. Of those, WebM only does the "costs me nothing to use on the web".
On paper, WebM is inferior technology. In theory, WebM's license is superior. But in actual, present reality, H.264 is really the best thing out there, and WebM is just not compelling enough to overturn the consumer apple cart in order to cater to the ideological whims of a small minority of consumers.
Google's hubris (Score:2, Interesting)
Google is exhibiting reckless behaviour because they think they're invincible, and it's all going to come back and bite them in the ass really soon:
1) Google "borrowing" Overture's ad-search business model, and paying them off not to sue them. I guess they got away with this one.
2) Google "borrowing" Sun's Java patented IP for use in Android/Dalvik with a Java-like language because they didn't want to pay for J2ME, not to mention the GPL code they slapped with an Apache license header. Oracle is fending to get payback, and I believe this case will be settled with Google either paying off Oracle with lots of money, or joining OpenJDK and paying license fees to Oracle.
3) GoogleTV, which is an attempt to serve ads over cable companies' signals. The cable companies are now blocking GoogleTV.
4) Google picking stupid fights with former partner Apple, including Android, NexusOne, Chrome and ChromeOS, leading Apple to develop iAd and go after HTC and others for patent infringement.
5) Google's end run around H.264's patents with a similar patent-encumbered codec simply to prop up Flash and screw up Apple serving H.264. Again, Apple is getting payback.
6) Google coming out with ChromeOS, Google Docs and corporate Google Mail. Microsoft hit back with Bing (although I don't see how this will succeed)
7) Google allying themselves with Adobe, having been a staunch supporter of web standards but now bundling Flash. If Flash won't cut it on mobile devices, as it still performs poorly on anything besides Windows and in 32 bit.
The day of reckoning is coming for Google because the world of computing is shifting away from the desktop at a rapid rate, and if Apple's iPad wins, then Google's ad revenue will dry up at the expense of iOS.
Let me be clear that I don't support software patents. Unfortunately, that's the way the game is played, this is accepted by all parties involved with large investments of capital made with an understanding of , and Google is trying to cheat. What goes around comes around, and Google is in for a rude awakening.
Even more IE plugins from Google? (Score:5, Interesting)
So.. I guess Chrome Frame was a success then? Strangely how the stats don't reflect that at all.
so let's see how the future will play out then...
On one side of the ring: H.264
* Solid native support on the default browser of Windows - IE9.
* Solid native support on the default browser of OSX - Safari.
* Solid support on the rest of the browsers via the ubiquitous (95%+) and well known by the public Flash player.
* Native support on mobiles.
* Formally approved standard by ISO and IEC
* Guaranteed free distribution on the web for free content, minor free for paid content.
* Vast amounts of existing H.264 content, widely used in video editing apps, broadcasting, recording motion cameras and so on.
On the other side of the ring: WebM
* No native support on the default browser of Windows - IE9.
* No native support on the default browser of OSX - Safari.
* Solid native support on the rest of the browsers.
* Spotty support on only some mobiles (don't expect it on Apple devices, Microsoft is on the fence).
* Not formally approved standard by anybody, just an open code dump at this point.
* Free to use, but questionable future if challenged by MPEG LA and others.
* Almost no existing WebM content, spotty or missing support in video editing apps, not used in broadcasting, not used in motion cameras and so on.
So uhmm, yeah, Google. I wish you guys good luck.
Re:Then has anyone decided to fork the H.264 build (Score:4, Interesting)
I think you might be surprised what supports OGG. It never says it on the box or, when it comes to car stereos, on the faceplate, but sometimes it is there. My car stereo that supports USB plays ogg, and it surprised me when it worked because there is no information anywhere that it would. It's free so it simply gets put in, and maybe in some cases the bozos in management don't even know it.
Re:But how will it be encoded? (Score:5, Interesting)
Define "important" & "near".
As always, it comes down to content providers (Score:5, Interesting)
The more things change, they more they stay the same. Once upon a time, we used to visit webpages and were told that we needed to download Real Player to view the content on the page. Then we needed QuickTime. Then we needed Flash. Now we are going to need WebM.
In the end, it doesn't matter what the browser vendors want to include with the browser. It will come down to the content providers and whether or not their content is compelling. If they are offering what consumers want, consumers will download whatever plugin they need. Downloading plugins is an established behavior.
The only group who will be affected by this at all are the developers. They have to make the choice as to what video encoding scheme they want to use for their applications. So developers out there, how many of you care? On one hand you know that if you go with H.264, all IE and Safari users (read 90%+ of computer users) will be able to view your content without downloading a plugin. You will miss out Chrome users (assuming nobody comes out with an H.264 plugin for Chrome). On the other hand, you can choose WebM and presumably avoid the spectre of maybe, possibly, one day (but not very likely) having to pay royalities on H.264. You end up with some portion of the 90% of the market who are willing to download a plugin. Which do you choose? Or more realistically, which one does your employer hoist on you?
Re:Even more IE plugins from Google? (Score:5, Interesting)
It's strange that so few people have figured it out.
Google is in the strange position that it got more bandwidth, more servers, more brains and more money than they honestly know what to do with.
So they use the money on more talent, servers and bandwidth, and let the people work on their own ideas part of the company time. Anything that looks even remotely useful (strengthen their position, gaining mindshare, get their ads in more places) gets thrown out there.
Examples:
Gmail. Google Wave. WebM. WebP. Chrome. Chrome Frame. Google Maps. Google Apps. Google Reader. Android. Translate. Android App Inventor. Google Body. Google Mars. Google Earth. Calendar. Code. Groups. News. Books. Picasa. Docs. Analytics. Website optimizer. SketchUp. Voice. Sky maps. Google Video. Trends. Talk. Buzz. iGoogle. Goggles. Scribe. Code search.
They're throwing an insane amount of random stuff on the wall, and then see what sticks. Some does, some does not.
They have more resources than they can reasonably use, and this is the result. Have an idea that looks fun? Some example code? Good, here are some money, servers and practically unlimited bandwidth. See if you can make it work. A bit later Google Cakes pops up, and maybe it will find a use. And Google earns some more information and mindshare. And a new place to splash targeted ads.
In the end, they make even more money, which they then put in talent, bandwidth and servers.. And the cycle continue. I sometimes wonder if they will hit a limit, or it will just go on and on.
Re:Then has anyone decided to fork the H.264 build (Score:5, Interesting)
>MPEG-LA has already claimed that WebM most likely infringes upon their patents. If you adopt it, you risk a danger that is actually likely and in MPEG-LA's interest,
In other words if they lose in the marketplace against WebM they will try to win the courtroom with their stable of bullshit patents like "drawing to screen web-based device" and "putting data in framebuffer of mobile device"
Stop defending software patents as being legitimate concepts in a debate over formats. They're roadblocks society has long overgrown. Suggesting that we should align ourselves with the larger mafiosio because he has more guns is stupid, shortsighted, and shows you to be a MPEGLA shill even if that isn't your intention.