As dejo has already pointed out Google is NOT dropping support for HTML5. Google is dropping support for H.264, a patent encumbered codec, in favor ofvWebM, an open, non-patent encumbered codec.
As dejo has already pointed out Google is NOT dropping support for HTML5. Google is dropping support for H.264, a patent encumbered codec, in favor ofvWebM, an open, non-patent encumbered codec.
On August 26, 2010 MPEG LA announced that H.264 encoded internet video that is free to end users will never be charged for royalties. All other royalties will remain in place such as the royalties for products that decode and encode H.264 video. The license terms are updated in 5-year blocks.
I was of the impression that there was a good chance that WebM infringed patents and was a little too close to H264 for comfort.
So does this mean they are going to stop supporting Flash? You know the one company proprietary product??!?!? In support of a more open format?
I absolutely love Gruber's response:*DING* Very interesting point that one isn't it? I know that many will forgive Google virtually anything but dropping H.264 support for not being an open protocol while still supporting Flash with nary a word of complaint sorta puts the kybosh on that excuse. No, this is an attempt to a) get users onto their prefered formats and b) weaken Apple's position in the market if they stick to their guns and don't support Flash. As is so often the case with stuff Google does it can claim it's in the best interests of the consumer while actually making things that little bit worse for them.
Point #5 was answered quite nicely by the good ol Macalope:John Gruber said:
- In addition to supporting H.264, Chrome currently bundles an embedded version of Adobes closed source and proprietary Flash Player plugin. If H.264 support is being removed to enable open innovation, will Flash Player support be dropped as well? If not, why?
- Android currently supports H.264. Will this support be removed from Android? If not, why not?
- YouTube uses H.264 to encode video. Presumably, YouTube will be re-encoding its entire library using WebM. When this happens, will YouTubes support for H.264 be dropped, to enable open innovation? If not, why not?
- Do you expect companies like Netflix, Amazon, Vimeo, Major League Baseball, and anyone else who currently streams H.264 to dual-encode all of their video using WebM? If not, how will Chrome users watch this content other than by resorting to Flash Players support for H.264 playback?
- Who is happy about this? ★
Macalope said:Adobe.
Looking at comments on the net, it seems the people most annoyed by this are Chrome users.
And for Google to presume all web publishers out there are going to re-encode all their content for a still new and untested video format that is only supported in one browser with a single digit browser marketshare? Are Google intentionally trying to kill their own browser or have they just become incredibly stupid?
H.264 is a stable, valid, and viable solution for the internet, and Google is promoting instead a crappy alternative which is probably going to turn out to be patent encumbered anyway. They've done no good service to web design, internet users, or their customers.In the long-term WebM will end up being supported by a lot of browsers, either through HTML5 for Chrome, Firefox and Opera, or through new versions of Flash for everything else. So WebM will be a viable choice should video providers be given a reason to move away from h.264. I'm not sure what that reason could be though, except for the MPEG-LA imposing real charges which they've said they aren't going to do for free video.
I would guess they are doing so to actively influence the market (placing whatever goal they have in mind over serving their customers).* It seems like something they would do in order to support Flash in some underhanded way, but I'm having trouble wrapping my head around Google doing something like this. I expect it would be something else. Perhaps they just want a video codec which they have more control over.I get that they would want to push people to use their own codecs, but why would they do it by REMOVING functionality from one of their products? I just think it's ridiculous that they had the support for h.264 and are now pretty much making their browser worse by removing one of it's features.
It seems to me as though several companies are waving around the word "open" (pretending it to be synonymous with good, honest, and not corporate) and using the HTML internet standards as a front to push their own ideals.
Apple was the first one- they (with google, their buddy at the time) pushed h.264 potential to support their future iOS ecosystem around it. The iOS devices depend on h.264 hardware encoding to save battery life. Google even went and changed YouTube to support h.264- which was huge and worked to legitimize the iPhone and its bold decision not to support flash.
Now, google split with apple and has developed their own mobile OS, which under the flag of openness supports more video formats (and uses flash) and does not benefit from strict h.264 usage. Could google's move be a stab at apple's iOS? Under the flag of "openness" muddy the waters to prevent h.264 from becoming a standard and having anyone have the upper hand in the mobile territory?
I admit that this is extreme skepticism and I'm sure my argument has technical flaws. Regardless of why google is doing this, it seems to me like this is a major loss for the consumer. I don't see any way around a year-long struggle for video format dominancy during which the consumer will suffer. Websites will likely either use flash, h.264, or webm. Apple will likely never support webm and google will likely push forward in removing h.264. What kind of battery life issues can we expect when manufacturers are discouraged from building in hardware video encoders without any clear standard in sight? Can we hope that website developers will make their web video compatible with flash, h.264 and webm?
I hope I'm wrong!
It seems to me that the ship has sailed for an "open" "standard". The holy grail of a perfect video format that works well, does great in mobile devices and is completely open with no threat of ever being encumbered with patents will never happen. Rather than screw the "standard" part for years ahead and screwing the consumer, lets give a little on "open" and stick with a "standard" so that the world can move on. Even if its not h.264 (and screw over our iOS devices (I'm presuming they are more popular around here), lets at least pick something so that websites and hardware developers can move forward and make better devices.
Promoting a free format could very well benefit customers, I don't think customers would be very happy to pay to upload videos to Youtube for example.Google's move is not something they've done for the consumerpeople need to at least get that sorted out.
Agreed. Supporting them both would be the more open solution.To be clear, I think Google should support them both, but the double-standard they're demonstrating is disheartening to say the least. It seems like every time they make a business move these days I find myself respecting them less—I used to admire this company.