With yesterday’s news that Google will be dropping H.264 support from the Chrome web browser, the internet was split in half. One one side, there’s people who applaud the move, who are happy that Google is pushing an open, royalty-free and unencumbered video codec (irrespective of Google’s motivation). On the other side, there are the H.264 supporters, who believe that H.264 is the one and only choice for HTML5 video. One of the most vocal and public figures in the latter group is John Gruber. Following his five questions for Google, here are ten questions for Gruber about WebM, H.264, and standards on the web.
Introduction
While Gruber’s questions to Google were classified as ‘simple’, the following ten questions are not, and for good reason. This matter has been brewing for a long time now, and it’s a very complicated issue – hence, questions and arguments about it will inevitably be complicated as well.
John Gruber’s arguments – posed over the years – are only used as a framing device. Since he is one of the major proponents of H.264, his views on the matter seem to quite accurately reflect that of the entire pro-H.264 group. These ten questions are meant to foster a good and thorough discussion of the matter. I chose the questions setup for exactly that reason: bite-size chunks we OSAlert readers can cover on a piece-by-piece basis.
While I doubt other sites will pick this up, it would be nice if they did. Discussion on this matter needs to take place not only on sites like OSAlert, but also on the large technology websites.
Ten questions
-
You proclaim to be a proponent of a standards-based web. The W3C, which oversees these standards and develops them, prohibits the use of technologies that are not royalty-free; hence, H.264 cannot become the standard for HTML5 video. Since H.264 is anything but royalty-free, how do you justify pushing H.264 if it is inherently incompatible with the standards-based web that you claim to be a proponent of?
-
Do you not see the danger in letting a technology that is overseen by a company run by a known patent troll become entrenched into the standards-based web? Do you think it is a good idea to let a known patent troll control video on the web?
-
Are you aware of the fact that every major chip manufacturer except for Intel have openly pledged support for WebM? Are you aware of the fact that hardware support for WebM is scheduled to arrive in Q1 2011?, followed by even more later this year?
-
Firefox has overtaken Internet Explorer as the most popular browser in the largest market (Europe), meaning that once Firefox 4 hits the streets, most browser users in Europe will be able to play HTML5 video encoded in WebM – but not video encoded in H.264. Are you willing to concede that – contrary to what you claimed yesterday – content providers would be better off providing video in WebM in 2011? I mean, browser makers – especially since Chrome on Android 2.3 also supports WebM – have clearly chosen for WebM, instead of H.264.
-
Related to #4: wasn’t it you who agreed with Robert Scoble when he likened Apple’s struggle to diminish the importance of Flash to Firefox’ struggle to diminish the importance of Internet Explorer (which ultimately succeeded)? Why is it that you are now using the same arguments against WebM that people used against Firefox?
-
Are you aware of the fact that On2 released VP3 before H.264 was released (2000 vs. 2003), and that therefore, the MPEG-LA most likely infringes on On2 (now owned by Google) patents? And that this is most likely the reason why the MPEG-LA has never been able to substantiate any of its threats, because they would most likely be sued back?
-
Are you aware of the fact that after a decade of threats by the MPEG-LA, they have never been able to show a single patent infringed upon by On2/Theora/VPx, despite offers by the Xiph Foundation to work together with the MPEG-LA to ensure no patents were infringed upon?
-
You are a proponent of Apple using its influence to diminish the importance of Flash for the web. Yet, when Google makes similar moves to rid the web of a similarly closed and patented, albeit different type of technology, you do not support them. Why is Apple promoting an open web a good thing, but Google promoting an open web a bad thing?
-
Do you think it is reasonable to expect makers of free products (Firefox, Chrome, Opera, and so on) to pay for H.264 support in their products? In other words, isn’t it entirely fair to expect makers of free products to use the financial argument to not include support for H.264? Or, as an OSAlert reader puts it, “if you are a company that gives away your product – how the hell are you supposed to justify paying for such a license when there is a perfectly good alternative that doesn’t cost you money?”
-
Why do you appear to be opposed to promoting an open, royalty-free, non-patent-encumbered video codec? Is it because said codec is currently not promoted by Apple? If Apple were to switch to WebM and drop H.264 tomorrow, would you then herald it as a great move?
Excellent questions especially concerning Firefox. Everyone who has responded negatively to the announcement seems to be forgetting that Firefox never supported H.264 and so if you wanted to support Firefox you had to encode in WebM anyway. Google’s decision will hopefully push the remaining browsers, Safari & IE to support WebM allowing for a single compatible encoding format.
Firefox supports h.264 courtesy of an installed Flash plug-in.
This whole point is about the HTML5 video tag. Nothing else.
I’m afraid Flash does not mean explicit h.264 support, despite what some people might think.
Au contraire, any installed Flash plugin is not Firefox.
ZNU said it best:
“This serves two strategic purposes for Google. First, it advances a codec that^aEURTMs de facto controlled by Google at the expense of a codec that is a legitimate open standard controlled by a multi-vendor governance process managed by reputable international standards bodies. (^aEURoeOpen source^aEUR != ^aEURoeopen standard^aEUR.) And second, it will slow the transition to HTML5 and away from Flash by creating more confusion about which codec to use for HTML5 video, which benefits Google by hurting Apple (since Apple doesn^aEURTMt want to support Flash), but also sucks for users.”
Ah, parroting Gruber. You could’ve just linked to either Gruber or the original Slashdot comment, you know.
Call it free standard if you wish. In the context of Open Web, open standard includes royalty free licensing.
Apple is not a supporter of Open Web. Adobe Flash is just a competitor, so Apple plays against them. The same reason they banned all other browsers (even open ones) from iOS. Nothing to do with openness or closedness. It’s all to do with Apple’s paranoid thirst for control and domination.
Don’t forget that Apple is part of MPEG-LA and they get money just from the widespread usage of H.264. The advance of WebM will weaken H.264 usage in hardware and software. I.e. it will kill the chicken with golden eggs which Apple likes to collect. So why should Apple speed up their own decline in profits from video codecs licenses? So stop this nonsense about Apple and Open Web.
Yet funny enough the <img> tag has no specified file format and people were quite happy to use GIF even with all the patenty goodness that came with the territory. Let the marketplace dictate what format rises to the top.
Wow… Congratulations for destroying your point all by yourself !
It’s precisely because of the Unisys incident (which happened due to widespread use of GIF) that so much people *don’t* want of a format encumbered by patents, obfuscated licensing terms and royalties on the web. And I’m ready to bet that it’s also because of it that the W3C now specifies that any web standard must be royalty-free.
Edited 2011-01-13 09:16 UTC
How have I destroyed my point? you’re demanding that W3C *MUST* specify WebM as the default format – I say that no format should be specified. The above scenario regarding png happened because W3C didn’t specify a format thus a multitude of formats came in use and supported hence it reinforces what I’ve said – allow the marketplace to decide.
Then we somewhat agree. H.264 is certainly not suitable for widespread use on the web, but there are several other present and future video codecs which could do the job, and the W3C shouldn’t cramp the spec by saying now “hey, you’re going to use THAT ONE !”.
My problem is that your example is terrible. If you want to advocate the solution used by the img tag, just say something like “At the time the specification for it was written, PNG did not exist. It is now proven to the best format for high-quality images on the web, with JPEG as a good second.”
Advocating the img solution while talking about GIF is like saying “Oh, the US legal system is perfect, and the lawsuit which that lady won against McDonalds perfectly proves my point”.
Edited 2011-01-13 09:30 UTC
True, 100% agree. I’ve since corrected my position based on information I’ve been provided by another post. I was under the impression with at least Mac OS X that h264 was provided by Safari linking into the QuickTime Framework (the Framework, not though the NPAPI plugin) but from what I’ve heard that isn’t the case which means the idea ‘just install a plugin’ isn’t a viable solution.
True – and WebM for all the hysterics put forward by some is actually pretty good when compared to h264 hence the ‘technological’ argument pretty much falls on flat on its face. My impression was that WebM support on at least Mac OS X could be provided through a QuickTime Framework plugin but I’ve since found out that it isn’t the case – that the Qtkit doesn’t provide a plugin infrastructure and Safari apparently is hard coded for h264 which makes the whole idea of ‘just install a CODEC’ an impossibility.
How about “Just install a decent browser”?
Because Firefox is shit on Mac OS X and Opera a walking joke reminiscent of 2000.
Erm…Chrome? Camino?
Edited 2011-01-14 15:07 UTC
If you like high CPU utilising battery suckage then be my guest. it is 2010 and one is still waiting for a 64bit build. Give me a 64bit build or GTFO.
It is still Firefox but with a nicer skin – other words it still sucks giant donkey balls.
I have the bad feeling you mean the coffee lawsuit. Let me disprove your ramblings :
http://en.wikipedia.org/wiki/Liebeck_v._McDonald%27s_Restaurant…
That was pretty damn justified. She got 3rd degree burns, needed skin transplant because they kept their coffee too hot. She wanted to have her hospital bills paid, she got the run-around, she sued.
Edited 2011-01-17 23:37 UTC
This comparison is silly. The gif situation shows exactly why a baseline image format should have been specified. We could have avoided the whole gif mess.
Controlled by Google in what way? I get to use it without having to hire a lawyer, I get to install it on devices and make as much content as I like and I have the full specifications and code so I can do what I like with it.
We’ve had these before. They’re closed clubs designed to lock out competition they don’t like.
A typical Microsoft line, interestingly. An open standard without an implementation people can guarantee is totally worthless.
h.264 proponents might be worried about it but it won’t worry anyone else. They’ll use what work on YouTube for the most part.
Don’t you know? ISO et al. are evil when they ratify a Microsoft standard, but holy sacred good when they ratify anything else using the exact same process.
Makes total sense.
I’m not entirely sure where that’s going, but no. A railroaded ‘standard’ is a railroaded ‘standard’. There is ample evidence that Microsoft has loaded ISO committees in the past simply to rubber stamp everything. The ISO should be putting the brakes on this kind of thing, but nevertheless, Microsoft was still to blame.
You can only guarantee a standard to be a standard that everyone can implement by getting on and creating an implementation that anyone can freely use anywhere.
That’s why ODF is worth a hell of a lot more than OOXML, but I digress. You can believe they were created by the same process if it makes you feel better in some way.
Nonsense. It is nothing but FUD.
It is not controlled by Google. Stop spreading lies.
It is NOT open. It is closed. Stop spreading lies.
No, but free of patent claims = open standard.
It’s better that it takes more time, if it saves the web from more closed crap like h264.
Firefox for Mac OS X and Windows supported H.264 via Apple’s Quicktime plugin as well.
What about chrome, it does certainly support NSPlugins. So it would be the same option here.
That would defeat the purpose of native video in browsers. Plugins can never be like native support.
He, like MG from techrunch are nothing but an extension of Apple’s PR machinery. To expect a rational discussion with them is a waste of time. They will agree with you if you agree with what apple is doing and will simply ignore you if your views are different from apple’s.
When will flash release a version with webM build in? Flash plays a critical role in mass adoption of this codec.
h.264 vs vp8 is largely not a practical problem for now since most people access h.264 content through flash and a switch from one codec to the other will be transparent to most of them. This could be one of the reasons google still has flash as one of their friends. Flash will help in easing the transition from h.264 to vp8.
This move greatly helps flash because now flash will be able to play everything “out of the box” and most web designers wont have to change anything.
Apple enthusiasts and idevice owners will be negatively affected the most and hence some of their complaints are understandable
I asked them earlier today on Twitter, no reply..
Probably because they never announced support for WebM.
Just support for the VP8 codec.
Which is why I asked about the codec, then the container.
http://twitter.com/johndrinkwater/status/25204868918542336
Though, from the reply, sounds like it is WebM coming:
http://twitter.com/jdowdell/status/25286855821889536
Well, it’s exactly official but here’s hoping.
When it makes them money. Releasing a version of Flash that will help obsolete Flash is not good business strategy.
WebM becoming a standard is a good thing for Flash. The html5 video tag doesn’t support DRM, streaming, ad-insertion or bandwidth switching… Companies serious about their online video will still need to use Flash.
And remember, Adobe makes more money off of Creative Suite than it does off Flash, and content creators always want easier and more streamlined ways of creating content. Adobe just demo’d the ability to grab animations/grpahics out of Flash and paste it into Dreamweaver… creating HTML5-compliant animations.
Adobe makes money by selling tools to developers and content creators. The more features they can add, the more often they can release software and charge devs.
Repeat after me:
*Flash is not just for internet video*
It has legitimate uses for vector-based animations and games, which are easy to make, and very amusing.
There is no alternative to flash animations and flash games (yet).
Killing flash video = good.
Killing flash = bad.
One can create and view flash animations and games with FOSS implementations such as gnash, so until there is an HTML5 alternative that allows the amusement of flash animations and games, we need it to stick around.
http://raphaeljs.com/
Edited 2011-01-13 08:44 UTC
Pure HTML5 games: https://mozillalabs.com/gaming/
Edited 2011-01-13 23:12 UTC
Playing video in Flash is one of hundreds of use cases the Flash Player is capable of, so let’s can this argument that HTML may some day play video without a plugin across all browsers, making Flash obsolete. Right now, Adobe is footing the bill for people to play their H.264 video by paying this licensing fee and then giving away their player. Something other companies (Firefox and now Google) aren’t willing to do.
Adobe, though suffering from some of their just deserts in being slow to fix bugs, has the LEAST going on here in terms of an agenda. They are just trying to push their authoring software. They have numerous products here that will author both SWF and HTML content, so they’re covered.
I agree 100% that Flash Player will help Google in this transition to WebM, and that those who will eventually suffer will be iDevicers. They have been duped by Apple and their sheep into believing the very thin openess arguments. The fact is, Google is adhering to what stands as the HTML5 spec by supporting both Flash, as it is a plugin, and plugins are in, and WebM as it is royalty-free. Both are part of the spec. The royalty model of H.264 is not.
Edited 2011-01-13 01:08 UTC
Why would WebM obsolete Flash but not h264? If one will, then so will the other.
First, I’d like to see flash not be the only thing that crashs on my computer several times a day due to pretty much any webpage having a flash advert on it.
Secondly, I really want to see supported 64bit version already.
At the moment, I have a great hate for flash and it feels like its just getting worse with every new version released.
Not to derail the thread Sagum, but what OS and version of flash are you using? I use flash constantly on Fedora 14 (the 32 bit version) and it very rarely crashes. When it does, it only crashes flash, not the OS, not even the browser. At most I have to reload the page. And it only ever crashes on videos.(usually when I have multiple videos going)
I personally haven’t seen Flash crash in… Well, ever since I started using Windows 7, I guess (release day).
It sometimes crashes on YouTube HD videos.
Here’s a query in Mozilla’s crash database for all plugin crashes during the past week alone:
http://crash-stats.mozilla.com/query/query?product=Firefox&version=…
As you can see for yourself:
* The top 100 entries are all the Flash plugin (“NPSWF32.dll” on windows, “Flash Player.plugin” on mac).
* The top crash signature alone gave 71,000 crashes during the past week. The second gave 9,800 crashes, the third gave 7,400 crashes.
* Crashes affects all operating systems, including Windows seven, e.g. http://crash-stats.mozilla.com/report/index/decf2420-f0a0-4975-8775…
Edited 2011-01-12 19:34 UTC
Of course the top 100 is filled with Flash crashes. It’s the only plugin people actually use!
I don’t think flash runs all that well on Linux in combination with opera (64 or 32 bit makes no difference to my experience). But as stated before, it only crashes once in a while when having a lot of flash ads + videos open. In firefox and chrome this seems to happen less, though I could just have missed it because I seldom use these browsers. Flash never ever crashed any of these browsers however! At least not in the last … 5 years or so?
Oh, and on Windows XP or 7, which I use at work, I never had a single crash either, regarless of the browser.
Edited 2011-01-12 20:15 UTC
I just ran into this the other day, and I found, on a 64-bit Linux install, Opera 11 32 + Flash 32 runs better then Opera 11 64 + Flash 32. Previously, Opera 10 didn’t have this problem, and a 32-bit install doesn’t seem to have the problem with Opera 11.
Firefox doesn’t seem to have the problems Opera does, but I’m running AdBlock which cuts down on the number of Flash threads.
I use Win7 and I’ve seen Flash crash a lot more in Firefox than Chrome or IE8.
The one advantage of IE8 is that it has the best version of Flash. Using IE8 for Flash videos can save you some battery life.
I’m surprised by how many people use Firefox. I’ve had the most problems with in the past few years.
Well, you first have to understand that it’s only recently that IE became an acceptable browser again from a user’s point of view, with IE8. IE 7 and IE 6 were really terrible (IE 7 especially).
For most people, Firefox just works. It’s not #1 cracker target, so it’s a better choice than IE for a cautious sysadmin. And it’s sometimes simpler to use than IE, too, e.g. when you want to setup something as simple and common as proxy settings you don’t have to go through a mess that’s nearly comparable to IE’s settings panel.
Sure, there are other browsers. But FF was there first, it works, it’s simple, it’s not branded by a megacorp having some bad reputation in terms of privacy, and as one of my friends (who used to use FF and now uses IE 8) says, “I just can’t get used to Chrome’s interface”. Some people love it, some people just can’t do with it.
Edited 2011-01-12 22:42 UTC
IE6 was really terrible? Thanks for the tip, this is my first day reading tech news.
Anyways IE6 was far worse than 7.
Most sysadmins choose IE for group policy. Anyone concerned with security should use Chrome. FF is overrated and I’m surprised by how many tech site visitors use it. It’s not as safe as people assume
http://www.zdnet.com/blog/security/mozilla-plugs-firefox-drive-by-d…
I realize FF has a bazillion extensions but I think it is more crash-prone than IE8 and I still hear complaints about memory leaks.
You miss the point. For a very long time, IE was such a terrible browser that even the average Joe would notice it. Opera was (and remains) a niche browser for geeks. Chrome did not exist. Thus, using Firefox was by far the most logical move.
Well, from a user’s point of view, I still think that IE 7 was the worst. I regularly had to use it at work, and I don’t remember having ever seen a browser freeze for a dozen of seconds when asked to open a window or tab except for these days, making me wonder if it had crashed or something. Bonus point for the extremely choppy scrolling. Then, there was the look, which was really horrible and totally out of place on XP, to the point where it was distracting. And finally, there were the toolbars which ate up lots of screen space for nothing but duplicating browser functionality, and which I didn’t know how to remove at the time.
I don’t ask much from a web browser. It just has to be responsive, have a clean yet simple interface which leaves much space for the web page, and work with most websites. Well, IE 7 proved to be totally unable to do such basic tasks.
Edited 2011-01-13 09:05 UTC
Serious sysadmins using IE? You made me laugh
If funny you should bring up that site for crashes. Because according to that link, Linux has suffered ZERO flash crashes. Thats right, not one. They are all Windows bugs. Now maybe that is because of Flash. And maybe its because its Windows. You would think that if they were so bad at coding, the Linux version of flash would have just as many problems.
Filter by Linux.
I second that, even though I use the 64-bit “Square” alpha myself. Because the 32-bit plugin won’t get installed anyway
-There’s an unofficial repo where updates to the 64-bit plugin are put as soon as they are available.
-For an alpha release, it rarely crashes. Only way I’ve found to crash it yet is to put it under a very high load (20 engadget tabs with videos or so).
-When the plugin does crash, it just leaves a gray rectangle in the browser. Browser session and OS are left intact.
-Please note that with this alpha you’ll get garbled sound on some flash videos (like nokia’s), though. That’s because Adobe devs don’t know how to use libc functions properly. Solving the problem is only a matter of find-and-replace, so the issue should be gone with the next pre-release.
Edited 2011-01-12 19:42 UTC
Windows 7, 64bit/nvidia gtx 280 (signed and beta). I’ve tried lots of different configurations as well. IE8/IE9/firefox 3x/4 Flash+beta + squarebox etc and altho, IE9 copes well (OS never crashed due to flash) the webpage flash control does cause the page to stop responding and IE recovers the page. and I currently have firefox without flash installed for pages that consistantly crash flash. But, most of the time, if a page is crashing the browser Tab. I can usually fix it by ending the FlashUtil10j_ActiveX.exe process….
But regardless, consumers just want it working and when pretty much every website has flash adverts, it needs to be working pretty much perfect.
Having flash crash out just because we’re watching videos isn’t good. i do find it seems to be when there are multiple adverts on the screen so it might be related to the same problem you’re having. however when I usually have at least 4 tabs open when browsing, the amount of adverts with some kind of video playing in them goes up, and is very annoying when i have to load firefox just to browse one page, more so when i’ve had to login as well.
i’ve been thinking about using a hosts file to block all the adverts, but i’d rather the sites to get at least a bit of impression cash back to help run the sites.
64bit flash has been available in beta since November. The more people that try it the sooner it’ll be released:
http://labs.adobe.com/technologies/flashplayer10/
Agree.
But there are actually only 6 questions there. The other four are just previous questions that were rewarded and not truly new questions. I’m guessing the article looked better with “10 questions” as compared to “six questions”.
Indeed. At least his questions were actually *questions*. This article is basically:
* Are you aware that WebM is way better than H.264?
* WebM is better than H.264. Why are you trying to say it isn’t?
* Do you not see why WebM is better than H.264?
* When did you stop beating your wife?
etc.
I would be REALLY surprised if he answers any of the questions. It would be kind of hard to answer them without looking like a complete ass or a total shill.
Has anyone ever seen John Gruber and Steve Jobs in the same room at the same time? Think about it…
The two sides of the argument are (a) those who value open technologies over closed ones, and (b) those who value technically superior solutions regardless of openness.
Now, I know some people are going to try to argue that WebM isn’t inferior to H.264. But it’s quite well known that H.264 has superior motion compensation, among other things. There’s a lot of subjectivity, but H.264 seems to compress at least slightly better or have slightly better image quality. Just accept it.
But see, technical superiority isn’t an argument to those of us who prefer freedom. Patents have prevented all sorts of superior technologies from entering common usage. Look up “arithemtic compression” on Wikipedia some time. Patents lock up all sorts of great things.
If you’re going to fight H.264 because of the patent mess, you have to make sure your arguements are based on things that are true. Don’t argue technical superiority. Stick to your point… the problems associated with what happens when patent trolls try to cash in.
The people who argue H.264 is better aren^aEURTMt those paying the licence fees. Not one.
License fees are passed onto the consumer. People who buy Blu-ray players, iPod Touches, Windows 7, etc… all wind up paying the respective company’s licensing fee.
I bought Windows 7 so basically I payed in part Microsoft’s fee.
Adobe figured out some business model that let’s them give away their Flash plugin and not go bankrupt.
Licence fees are _also_ paid by anybody broadcasting H.264 content for commercial use. Gruber doesn^aEURTMt pay it. He probably should be, but he^aEURTMs chosen not to.
So how can he be in support of H.264, but not willing to pay for a commercial licence since his website is his source of income, and therefore commercial.
Since when has Daring Fireball published video – in any format?
What on earth are you on about??
“Adobe figured out some business model that let’s them give away their Flash plugin and not go bankrupt.”
LMAO – It’s called selling software, Einstein.
Other than the Flash plug-in, Adobe develop one or two other applications… Photoshop, Illustrator, Acrobat, InDesign etc…
You might have heard of some of them.
Ah, good point. One other thing that makes technical superiority take a back seat… the cost!
I think the default encoder for H264 actuallty produces worse result than VP8. H264 is currently getting better results due to the open source encoder x264, but unless I am mistaken some the main developers in that project are attempting to port it to producing VP8 video streams. If that happens I doubt the difference will be anywhere near as big. They videos are using the same basic math, just different permutations of it (this is also what makes the patents issue so vague).
What ‘default encoder’?!?
The technical point is always valid when it comes to technology. What I argue against is tunnel vision idiots who consider 1% better to be “The Best” and nothing else matters. These seem to be the vast majority of opponents.
Whinny bitches who can’t get passed “Why would you use something technically inferior?”. An objective piss off to you.
Just on this point … I don’t accept that entirely.
It IS true that H.264 has superior motion compensation, because WebM sacrifices accuracy of high-motion as part of its strategy for high compression. WebM produces blur in areas of high rates of motion. H.264 doesn’t, it is sharper in areas of high rates of motion.
H.264’s strategy to achive high compression is to “guess” what the picture should be. This produces artefacts … elements of the picture which aren’t actually there. It is sharp, but it is inaccurate … it is a sharp picture which includes some things that were not actually present in the original scene.
At exactly the same compression level, WebM produces blur in areas of high motion, and H.264 produces artefacts. The question is, then, which is the highest quality?
H.264 will register a slightly better score against computer-based assesments of quality such as PSNR, but the thing is, the human eye will actually see things moving quickly (high rate of motion) as blurred anyway.
This is something that H.264 supporters will NEVER tell you about.
Edited 2011-01-13 04:55 UTC
There is only one side if you want something on the web. The web needs to be open and patent-free. That disqualifies h264.
Quality isn’t important anyway. VHS/BetaMax, CD/SACD, MP3/CD, Wii/PS3 etc. There are numerous examples where “inferior”/”lower quality” technology won.
Except, of course, there’s hardly any difference when you look at h264 baseline, which is what everyone is using. And again, quality is irrelevant.
While these are all good questions, Gruber’s questions still remain valid. Why does Google support H.264 through YouTube and Android? Why is Flash allowed? It’s hard to see this as a purely selfless “support open standards” move. Maybe I’m just cynical, but it sure looks like Google is doing this only because they think there’s an advantage in it. I don’t know what that advantage might be, since WebM is free, but they must have some ulterior motive.
His final question is a good one, too. Chrome had a distinct advantage over Firefox and Opera. Now it’s gone. Most people just want their browser work, and don’t care about the underlying technical issues. (I also really wonder about Apple with Flash. How can you leave your customers unable to access so many sites?) Why not have both?
Quite right. But even if it^aEURTMs a completely selfish move, does that mean that you have to pay to encode and broadcast WebM? No. You still win^aEUR”we all win^aEUR”regardless of Google^aEURTMs motive here. A web that uses WebM instead of H.264 is still a better web, regardless of who does what in it.
Maybe they are trying to cut off the spread of H264 to HTML5 video early on. Flash is already there and it’s hard to unseat Flash.
The answer is probably because the industry is still in transition. Companies (in particular, hardware companies) are currently adding support for VP8 and WebM, and other browsers are also catching up. I would expect that other third parties such as those with video encoding products are working on it as well.
Once the infrastructure is complete, I would expect that there will be wholesale moves to WebM to bypass all the royalties, and Google will naturally begin phasing out all H.264 support.
No, they are FUD from an Apple fanboy.
Because it was the only format until now. Also, h264 can still be used for offline video. This is about web browsers.
Because it’s everywhere, and it’s just a plugin, not a native browser feature. Google never said plugins are a bad thing.
No, it sucks as much as the rest of them.
In 9 years, I’ve never had Flash crash on any of my machines.
I thought I might have once, 5 years ago. It turned out to be some poorly written add-ons to I.E.
… and he probably wouldn’t mind doing some nasty things to Steve Jobs.
It is really beyond me why people read the crap he writes.
Sometimes, I wonder if John Gruber actually does exist.
And if he does, whether he is actually the kind of guy he pretends to be, or rather some PR guy of Apple specially trained for the job.
Conspiracy theories FTW !
Indeed.
If somebody is a known shill on a their opinion becomes essentially worthless because it isn’t an opinion. It mystifies me that people even bother to read when they already know what is written on his site.
Edited 2011-01-12 20:31 UTC
The weird thing is that while reading the article, I wondered “if this guy, the same who changed sides about UI conformism, is indeed saying what the article reports, isn’t Thom giving him more exposure?”
EDIT: I forgot: someone said in an earlier comment that JG’s income is through his website… I didn’t even know some people are blessed with earning their life via their weblog. What was he before that point? a programmer? a PR person? a tech journalist?
Edited 2011-01-13 13:33 UTC
Yeah – he doesn’t write anywhere near as elegant or classy as you, you puerile maggot.
Fok jou.
The article’s a little hyperbolic and has some inaccuracies.
1.) strictly speaking, h.264 and WebM are equivalent with respect to royalties and patents with the exception one of the holders of VP8-related patents (Google) has given public license to them; WebM will be cheaper, but not free. The royalty-free nature of h.264 is now set to expire in 2014, but so will many of the patents covering it.
2.) MPEG-LA wouldn’t be a patent-troll per se. They were formed by the consortium of the technology developers and original patent holders and they’ve always been up front about their claims.
3.) Is correct, but it’s not clear why it’s important. It will take a few years before the technology is pervasive, at which time it probably won’t be relevant.
4.) Some browser makers. However, web browsers make a minority of the video distribution and production space. Almost all modern video tech outside of the web is based off h.264.
6.) VP3 is improperly compared to h.264. It’s much closer to ISO/IEC 14496-2 which came out a year prior to VP3. ISO/IEC 14496-2 (h.264) are most closely comparable; they are contemporaneous and use many of the same technical approaches.
7.) This overlooks the fact that perceived patent issues with VP8 and it’s predecessors contributed to the sale of VP8 to Google.
9.) It’s a loaded question. The browser should rely on the platform it runs to provide support for codecs. The only reason this conversation exists at all is because some want to move responsibility for implementing video codecs directly into the browser itself instead of the operating environment (the idea being that it might simplify implementation and consistency).
10.) I don’t think Apple cares, honestly. They use h.264 because everyone else does. Their platforms offer video playback and transcoding through a common API and a codec plugin architecture (as does Microsoft). Adding support for WebM really only requires pushing out the codec in an OS update (or an OS X download). You don’t find WebM anywhere yet, thought, so why add bloat?
The arguments are kind of silly. Google has good reasons to push for adopting a codec wholly controlled by them as the de facto standard. It gives them the ability to be the sole arbiter on matters of DRM, etc. For Apple and Microsoft, it’s pretty much an annoyance. For the video production and distribution industry, it’ll be an enormous pain in the butt.
9.) It’s a loaded question. The browser should rely on the platform it runs to provide support for codecs. The only reason this conversation exists at all is because some want to move responsibility for implementing video codecs directly into the browser itself instead of the operating environment (the idea being that it might simplify implementation and consistency).
Hooking to system APIs is fine for a browser aimed for that platform but it just simply doesn’t suit a browser that is aimed at being consistent on multiple platforms. Like for example if Firefox hooked to system APIs one couldn’t anymore say “works on Firefox”, they’d have to say “works on Firefox if [condition]”
Secondly, it would indeed create lots of extra work. At the moment if there is a problem with one or another feature and they get a bug report then it’s quite easy to find, but if they hooked to native APIs and there was a bug somewhere there Mozilla would get lots of bug reports that actually have nothing to do with Firefox. Ie. it would mean lots of bogus bug messages and more work to sift through all of them. Not to mention the work needed to support all the different APIs. It does all add up to quite a lot.
And yet every single cross-platform browser hooks into system APIs for many other aspects of their functionality, such as accessing files, drawing windows, etc. This is done through shim libraries.
Yes, it would create some extra work, but I’m not convinced it would be all that much. All that’s required for each platform is a fairly thin shim library that converts to the OS provided media framework. The functionality of all media frameworks is largely equivalent and generally very similar in functionality.
In contrast, cross platform game developers write engines that use either DirectX or OpenGL for rendering – the differences between how those two libraries work, especially in their latest incarnations, is an order of magnitude more complex than media playback, yet they still manage just fine.
As for bug reports, the crash logs would clearly indicate where the error occurred.
Games have not traditionally been high value targets; they do not provide the easy point of remote attack that web browsers do. They don’t offer the same opportunities for accessing the same numbers of users when compared to access points and user counts among website viewers.
Historically, games have tended to be more buggy and quicker to push out of active development and maintenance. Game hits shelves, people buy, vendor maintains a few generations of patches, game version 2 hits shelves, people buy, vendor moves developers over to maintaining game 2 leaving game 1 unsupported. They are short lived; they only need maintain the illusions for a few times through the story until the user stops playing through it and/or moves on to the next greatest-gotta-have-it blockbuster title. I’ve personally got a growing list of games that are long since abandoned by the applicable game publisher.
Between showing a smaller remote attack surface and being meant for a shorter period of use and support, games have not justified the efforts that browsers justify in securing. Browsers affect more users and get a whole lot more attack attempts per user session.
The grey area remains things like World of Warcraft where the game is tied to a network stream and central servers. In that case, you are opening your customers up to greater chances of remote attack versus self contained games that function without validating against a network server.
It also restricts new competitors coming in with new devices and new software systems, since they’re obviously not going to have h.264 and will need to get it – if the oh, so open consortium of competitors decides to be nice.
Not as many as your post…
That is based on your assumption that WebM is encumbered by patents that are not owned by Google. Google doesn’t believe there are any. Also, that last sentence should read “The royalty-free nature of non-remunerated (i.e. free) content over the internet is now set to expire…”, but nice attempt at trying to cast that net over the whole thing.
They are run by one (Larry Horn) according to the linked article, which was the point being addressed I believe. I’ll leave this one alone though as it doesn’t make much difference to me.
You will need to explain that one further if you want to convince me. MPEG-2 is still widely used after over 15 years, and while its use is waining there is no reason to believe webm won’t be relevent for just as long.
So what? What exactly does that have to do with HTML5? I don’t see how that is relevant at all.
Im not even going there. This whole “who had what first” line of reasoning is pointless – none of it means squat unless there is a lawsuit at some point. We’ll see.
Show proof of that. I’m not saying your wrong, just that I have never seen evidence that On2 believed they were infringing.
Total bull. Ive seen this argument so many times it makes my hair stand up. That whole line of reasoning is nothing more than a clever ruse to hide the fact that it isn’t possible for an open source or free to the user product to implement h.264 legally – the license as it is currently defined simply doesn’t have a provision in it that would even allow for such a product as it is explicitly defined by sales… So you say “Let the OS do it”, which in reality means “you don’t make money so you don’t even exist to us – you don’t matter”.
The best place to implement the video stack for HTML5 is in the browser itself. Google does it this way, Opera does it this way, and Mozilla does it this way. IE and Safari have their reasons for choosing to use the system codecs, which are plainly obvious to anyone with a brain.
Nice dodge. They care because:
1. They are part of the h.264 patent pool.
2. They use h.264 extensively and almost exclusively.
3. They are backers of a streaming standard that uses h.264 exclusively, and it is the only streaming method they officially endorse for use over 3G (HTTP Live Streaming)
In fact I would go as far as saying that “they don’t care” is about the most dishonest thing you posted here – they absolutely care.
How is it “controlled” by them? I thought other people had patents on it
Regardless, it is BSD licensed, the minute the published that license they lost all control over it. For anyone wanting to write free software that encodes video for web distribution, it is the only game in town.
I’m not going to get into a pissing contest about one or the other of these formats winning or whatnot, its irrelevant. At worse WebM causes a minor dent in MPEG-LA’s protection racket, it isn’t going to have any affect on the broadcast world or most hardware devices, Apple will likely never adopt it so it will be relegated to Android for mobile, it will always be a red headed stepchild when it comes to Windows, etc. etc. I’m not naive enough to think that it matters at all in the grand scheme of things. But it does matter to people who do not want to get dirty hands from dealing with the likes of MPEG-LA.
Google claim to believe that VP8 does not infringe on any third-party patents, but they don’t offer indemnity to companies planning to use VP8, so apparently the belief is not held with much conviction.
If they released some analysis of their patent clearance check I might place more weight on their claim. There are a huge number of patents covering all conceivable aspects of a video codec, so I am extremely skeptical that VP8 does not infringe any third party patents.
MPEG-LA doesn’t offer indemnity for h.264 either… I’m no more inclined to trust a cartel of technology companies than I am to trust one. In other words I don’t trust any of them. Frankly either or both codecs are equally exposed to the risk of a black horse patent infringement claim.
I’m not trying to be snarky. It is obvious that WebM does carry some risk since it is very similar to h.264 conceptually and the patent landscape for video codecs is a minefield. However, the whole “they don’t offer indemnity” argument is bullshit – no one does.
The reality is it doesn’t really matter whether or not WebM infringes on MPEG-LA patents or not. What matters is if MPEG-LA can mount an effective patent infringement lawsuit in the climate that Google is creating. It isn’t a moral question, no one is right or wrong. Software patents are the real problem, not who has which ones. Assuming MPEG-LA can actually come up with a clear case of patent infringement the questions become:
1. Can they sue successfully without alienating half the industry (including some of their licencors)?
2. Does Google hold patents that they infringe on, and are they willing to lose their entire patent pool over this?
3. Is there enough upside (i.e. money) in it to even bother.
These are all significant questions that are highly relevant. I don’t have answers to any of them, but at this time I’m inclined to think that the most likely scenario is MPEG-LA is going to sit back and do nothing, but you never know.
If they do proceed with lawsuits WebM could quite conceivably be destroyed in the process (and so could MPEG-LA). That is a real possibility. Lots of companies could lose lots of money and time, and there would be a big stink over it.
Guess well see what happens.
Edited 2011-01-13 17:16 UTC
It’s true that MPEG-LA does not offer indemnity, but the fact remains that many businesses holding essential claims for H.264 have found it joining the patent pool preferable to engaging in risky litigation.
Regardless of what ‘climate’ Google creates, each patent has a presumption of validity regardless of whether the invention is embodied in software or hardware. Furthermore, any rights holders who allow their patent rights to be infringed (perhaps in the hope of letting damages accrue) risk losing those rights under the doctrine of laches, so an incentive exists to sort this out sooner rather then later.
Finally, I have to say that the MPEG-LA is actually doing everyone a favour by starting a patent pool for VP8. Dealing with a single company to obtain a license is vastly preferable to identifying each company and separately negotiating licenses.
A world where VP8 requires royalty payments is a world where VP8 may as well not exist – being royalty free is the only attribute it has that that anyone cares about. It either survives royalty free, or it dies. If MPEG-LA creates a patent pool for it and starts going after people, the issue will get hashed out in court. If an MPEG-LA patent gets upheld in court against a VP8 implementation… well it is dead as a doornail.
Please stop peddling this lying-through-your-teeth bullshit about “doing everyone a favor”… The purpose of a VP8 patent pool would be to kill it – not do anyone any favors.
Ah but this a key point – a world without royalty payments is a world where neither VP8 nor H.264 would exist. VP8, as you know, was created by On2 technologies. In a world without royalty payments, On2 technologies would never have made that investment in the first place and VP8 would not exist.
As for your second point, the patents exist regardless of whether a patent pool is formed or not. Any rights holders who wish to kill VP8 would never join the pool. That is independent of the MPEG-LA.
Whatever… Software patents cause immeasurably more harm than good. If software patents didn’t exist neither would IP royalty payments – do you think all innovation would stop? I have nothing against people making money with software – its fair and reasonable to charge someone money for rights to use an implementation of software, but patents hurt the software industry more than they ever helped. They don’t foster innovation, they stifle it.
VP8 is royalty free. Its value is that it is royalty free. Were it to become not royalty free, it is practically worthless to anyone (including Google). Hence the only reason to form a patent pool for it is to make it worthless, i.e. kill it.
But you already know this…
My original point was that no evidence has been provided that VP8 does not read upon any non-Google patents. Until such evidence is produced, stating that VP8 is royalty free is premature.
Regarding your point about software patents, yes plenty of low-quality patents are granted, but is that an argument to declare one area of subject matter unpatentable? To me, it is an argument for improving the examination process.
You have not murdered your girlfriend. However, as long as you’re alive, you may still do it. As such, I’m going to state that you could be a murderer.
Edited 2011-01-14 15:37 UTC
Wowzer.
Point == valid.
But you didn’t need to “FACE!!!” them so _harshly_, Thom.
The MPEG-LA cartel has been whining about patents in VP8 for ages. And yet they have not made a single move. All they have is FUD.
And software patents are evil, period.
Guilty until proven innocent right? By that line of reasoning calling it royalty free isn’t premature – it is impossible…
You must be reading someone elses comments or something. I never said anything at all about patent quality – I said software should not be patentable period. The concept is both practically, and ideologically flawed when applied to software, and it does more harm than good. I don’t think improving the examination process is going to help much there…
It may be time consuming, but it is not impossible. Technology companies regularly conduct ‘clearance checks’ on products to find any patents they may have to license to sell their product. All I’m asking is that this result of such activity be made public to give other users of VP8 some assurance.
The legal basis for patenting software is well established and accepted in all jurisdictions that I am aware of. The reasoning goes that a general purpose machine running a claimed process (i.e. a software patent) becomes a special purpose machine, which reads upon that claimed process.
Now you introduced software patents into this, not me – so I can enter my opinion re examination if I want.
I have never seen MPEG-LA publish a clearance check for their patent pool… Do you have a link to such a document?
Firstly, a clearance check is performed on a product or process, not on a patent pool. Learn your terminology.
The MPEG-LA do not state that H.264 is a royalty free codec, so they do not have a burden of proof to support this statement.
What they do state is that patents in their pool are essential for implementation of H.264. This statement is supported by the following document:
http://www.mpegla.com/main/programs/avc/Documents/avcCrossRefChart….
If they were to state that these are the only essential patents for H.264, for this statement to be credible they would need to provide a additional analysis to show which patents, although close to H.264, were in fact different and therefore non-essential.
I’m sorry, “for h.264“… That better?
So let me get this straight…
Google is essentially saying: “here you go, you can use this and do not have to pay me for it, but I don’t make any guarantee that someone else doesn’t hold a patent on it and might sue you over it”
MPEG-LA is saying: “here you go, you can use this if you pay me for it, but I don’t make any guarantee that someone else doesn’t hold a patent on it and might sue you over it”
Why would the fact that in Google’s case the patents are licensed by them royalty free make any fucking difference at all to whether or not you would want to see such a clearance check?
You are asking Google to do things that MPEG-LA themselves do not do…
And they do not do that do they? In fact they explicitly state all over the place in legally binding language that they make no claim as to holding the only essential patents. If says so right at the top of the document you linked.
Where are you going with all of this? You seem to be arguing in circles. I don’t care about patents or patent law, and I am certainly not enjoying discussing it with you. Do you have a point that makes sense or not?
Perhaps you’d enjoy this conversation more if we just had a circle-jerk about how software patents are ‘teh suxorz’?
I’ve made my point and if you are too stupid or lazy to comprehend it, then that is your problem.
I’m not so sure. When you have a format like this that a major video site uses, a format that everyone uploading to there will use and a format that anyone has the freedom to implement these things have a habbit of encroaching like sand filling in a lot of crevices.
That’s what the MPEG LA is worried about and why Gruber, Apple and Microsoft have ratcheted up the rhetoric. Once the pillars fall down that keeps the exclusive control of a club intact it doesn’t have much of a future.
I’ll concede that it is a possibility, but I don’t see that happening in the commercial video world. H.264 is highly entrenched, and for the big companies using it commercially the licensing fees are easily recovered through sales. H.264 also has a significant advantage when it comes to tools and flexibility, and that isn’t going to change for quite a while if ever.
Commercial broadcasters and distributors for the most part want to buy tools, because they want support contracts from their vendors. WebM is going to take a long time to penetrate there (if ever) – and the only advantage it really offers is the elimination of licensing fees, which frankly are not that much for the Sonys and Toshibas of the world.
You’ll notice I have never said I thought WebM was a better format technically – that is because imo it isn’t. It probably never will be, but it is certainly good enough for most uses. I think the simple fact that it is open and royalty free will create an environment where tool development will become highly accelerated over the course of this year. By 2012, we should have some pretty good open source tools for WebM. Enough that a thriving video ecosystem for non-commercial video becomes possible.
I personally think what will end up happening is WebM will take over the non-commercial video world, but will have little if any effect on the commercial video market. But you never know…
1.) I think you are hyperbolic here. Won’t even bother.
4.) You know why WebM is called as such? The discussion is about the future of the web.
9.) If you want your browser to use OS codecs use one that does. This whole discussion doesn’t apply to you anymore.
10.) You’re kidding, right? Nobody should even try to innovate then.
One reason for implementing support within the browser is security; the browser is a huge target and easy access point into the OS.
– if browsers feed content to the OS media framework a successful exploit (malformed media content) gains access to the entire OS. Play exploit against vuln in the OS framework and you pwn the OS.
– if browsers play content internally a successful exploit may be contained within the browser’s own sandbox; it does not rely on things outside it’s own security sandbox. Play exploit against vuln in the browser and you pwn the browser, not the OS.
IE had a vuln in the system wide ANI related library; any program that displayed an animated mouse pointer was exploitable including IE. Use a malicious mouse pointer within your website and you would be able to feed stuff directly through IE into Windows.
Exploits against Flashplayer have also allowed people to break out of the browser into the greater OS. Flashplayer runs externally from the browser so bugs in it affect more than just the browser.
1) H264 is closed. WebM is open.
2) They are patent trolls.
4) Web browsers are needed to view video on the web, which is the context here. Pay attention.
7) Quit it with the FUD. No actual patent claims have been filed for VP8.
WebM is not controlled by Google. You Apple fanboys need to stop lying.
I think people are getting drawn into pissing matches unknowingly.
It’s clear that Apple and Google have made their decisions on flash and HTML5 based on business. In reality they are both doing the same thing IMO.
To see Apple’s stance is to understand that they are making plays based on mobile computing and not the desktop. Basically, if it’s hardware accelerated, low cpu load, and excellent quality, Apple wants it. H264 fits the bill moreso than Flash at this point. WebM doesn’t come closer than Flash.
Gruber’s questions are pretty useless and not particularly relevant to the topic. Android support of H.264 has little to do with Chrome other than being owned by Google. Flash, while used for video is not related either. It isn’t used through HTML’s video tag, it is an object or embed (however they’re doing it these days). It’s a fundamentally different technology, though that doesn’t mean it should be bundled either. Netflix and Youtube seem to cloud the discussion, too. To any browser, Netflix is hardly using H.264, it’s using Silverlight or nothing. The other sites, I’m not sure.
To me, this raises a better question: Chrome isn’t a serious browser, it’s only raison d’etre is to make tracking everyone that much easier and making Google’s job of marketing to you that much easier. The questions we should all be asking is how to escape Google’s grips and not stupid crap about some proprietary video codec that you shouldn’t want to use anyway.
Run chromium if your worried about it (all the phone home stuff is removed). It’s easy enough to find builds for your OS of choice. Really, saying it isn’t a serious browser is downright silly – it is a very very good web browser.
By that I gather you mean the group who support H.264 because it is an internationally recognised INDUSTRY STANDARD, that is used in every other major form of digital content delivery, AND has consistently delivered a superior end product?
So how much does Apple profit from reducing the web’s dependency on Flash? How much does Google profit by forcing a WebM standard on everyone? The answer to the latter is very very obvious, and multi-pronged. The former not so much. Then there’s the proven performance and battery life issues with Flash, that have only been partially addressed after Apple took the stance. And comparing Apple’s influence on the web to Google’s? Please – you’re kidding right?
What about this one – that’s conveniently overlooked by the “we’re not going to pay royalties” brigade. Currently commercial video is encoded using H.264 for a variety of media. What additional costs, that will be passed on to the consumer, will be involved in “retooling” then creating and maintaining new production workflows to spit out WebM encoded video purely for delivery by a Google dominated web video market? How will those costs compare to the current fees associated with using H.264? I personally believe this will be a double-edged sword, but as there are currently no royalties being charged for H.264 for private web use anyway, I thnk the ultimate situation will be an increase in cost of commercial video delivered via WebM.
Of course private video will remain free, just as it currently is, but of course “we can’t trust them”. We can however trust Google, so they tell me…
If it is “Commercial” video, it means it is being sold to end users either directly or through subscription. If that is the case it is almost guaranteed to be DRM’d in some form (i.e. Netflix, Hulu, PPV services, etc.). None of these enterprises will likely ever deliver their content using HTML5, because neither the <video> tag standard nor webm allow for DRM currently. So having to “retool” for webm is a stupid argument – flash and silverlight are the only solutions for these people currently, and will likely remain so for the foreseeable future – neither of which has announced any plans to drop h.264.
Some distributers may choose to switch to webm assuming said players incorporate support for it in a manner compatible with their DRM schemes, but there will certainly be no pressing need for them to do so. They would, however, save the licensing costs of h.264 so I would expect at least some of them would choose to do so quite willingly if the opportunity arises.
In a nutshell, your scenario is a fairy tale.
Commercial video will never be delivered in webm…
I don’t trust Google. I trust the license webm is offered under. That simple.
Edited 2011-01-12 23:19 UTC
Just because h.264 is a standard doesn’t mean its worth crap. Just look at what Microsoft did to the ISO to get OOXML through. As for it being superior, maybe. streamingmedia.com did an analysis of the two. And while h.264 was better looking in still frames, I am not convinced it is something you would be notice in full motion video. Its certainly not better enough that we ought to get into bed with a known patent troll.
Apple has a lot to gain from the fall of Flash. Mainly, more people using Apple Xcode to code for their mobile devices. There is also the increased use of h.264 by the web. Google doesn’t care about flash. Flash is available for all platforms for free and it will never make it into the web standard anyway. But Google does care about having a royalty free codec available for the world and open source to be able to ship in its products.
Private video? Whats that? That would be only stuff you show on your own computer. Any site that hosts video and has ads is not private and therefore the license won’t be free. You can also bet that those terms only apply to the decoder. To make video, you are going to have to license the codec. But you don’t have to trust Google. They open sourced the codec. So it will be free no matter what they think about doing in the future. We already KNOW that the terms for h.264 will be changed in the future.
Are we really talking about H.264 Baseline here ?
It is not an open standard, and the web requires open standards. And it is not superior when it comes to the web because it is incompatible with the W3C’s patent policy.
Stop being dense. Google isn’t forcing anything on anyone. This move by Google has been welcomed with open arms by open standards advocates.
Only the Apple fanboys are hypocritically whining about it.
No, ignorant child. Having to pay royalties is incompatible with open web standards.
WebM is owned by an open-source project, not by Google. You fail again.
Edited 2011-01-14 22:19 UTC
Maybe Apple has a contract for Google (YouTube) to keep H.286 for x number of years…
Can’t somebody object to removal of support for one codec, without being opposed to the support of another?
The point is that H264 is widely adopted already, and now one browser decided to drop support for it, even though it was already there.
The two (opposing one codec and opposing the removal of support for another) are entirely unrelated.
Hey, honestly I agree with you on principle. I personally do not care at all if Google continues to offer h.264 or not. I’m no fan of promoting it, but at the same time I do understand and appreciate the technical advantages it offers. All the arguing is over the fact that in the end it is not the internet community’s decision to make. You may not like the fact they are pulling h.264 – that is your prerogative… but they are not taking something away from you, you never had it in the first place – Google was simply subsidizing it on your behalf (at least as far as their use of it goes).
The same applies to every company using it. h.264 is not free, it costs money at every level of distribution with the exception of last leg delivery of free internet content. You pay for it every time you buy a bluray disc, TV, DVR, set-top box, or rent/download a movie from the internet. The one place where it is impossible to pass the cost off to you is open source software/free software (i.e. Chrome, Firefox) – something Google is heavily involved with on many many levels…
Edited 2011-01-12 23:40 UTC
The point is that h264 is a closed standard, and therefore incompatible with the web. It should be removed from the web.
This OSAlert article is a little iffy to me. Some of the questions are little pathetic. Don’t flame me it’s just my opinion. Hey I am all for open standards but you H.264 is a standard in the video world and to remove it from the browser is just plain dumb. To make content makers encode the same video with multiple codecs is also dumb. Think about all the waste of storage, time and bandwidth. That’s what Google proposes though.
With that you completely ignored Gruber’s 4th question. I will quote it here for ya:
Sorry but it does not seem reasonable to the content providers just because Google has a bug up its butt.
I get that these are FREE browsers but don’t mistake FREE for non-profit as these free browsers are bringing in ad revenue and that is nothing to sneeze at. So free, in this sense isn’t an excuse.
Free is EVERYTHING! I don’t mean free as in no cost. The only way that open source browsers can support WebM is if it uses a free codec. Otherwise it will never happen. And considering most browsers in use ARE open source, isn’t it really Apple and Microsoft who are being a bit inconsiderate?
Edited 2011-01-13 01:39 UTC
Nah. Don’t forget that the rendering engine behind Safari is Open Source. So if Webkit supports it then so will Safari. IE is well, IE. I don’t have a problem with Microsoft making their own browser either. It is FREE, even if it is closed source, so it matters not in that avenue. Is MS and Apple being inconsiderate for not having Open Source OSs? No, OS X does not count because only parts of it are. I don’t think they are because they are a business trying to make money, after all.
H264 is a closed standard. That makes it incompatible with the web.
They already are! They are offering videos in several bitrates and resolutions. They might as well do it in an open format.
And you are forgetting that Google is one of the biggest video content owners, through YouTube.
What utter nonsense. Google is a content provider too!
Did I say that it was an OPEN standard? No I said it was a standard and it is. Just because a standard is closed does not mean it is incompatible with the web, THAT is nonsense.
No, you seem to have trouble reading. The article said encoding (codecs) not bitrates and resolutions. [/q]
And you are forgetting that Google is one of the biggest privacy offenders too and has their hand in everything related to the web. They have too much power, IMHO.
Thank You. Is it nonsense to Netflix, Vimeo and the others, not to mention the MAJORITY of consumers who do not give a crap if a standard is open or closed only that one day they are going to get a message that they can’t play the content because of Google playing internet lord. Consumer confusion is always good, isn’t it and no big deal either huh?
Just my Opinion, and you obviously don’t agree with it and thats up to you.
Edited 2011-01-14 20:32 UTC
Actually, that is exactly what it means. Look up the patent policy at w3.org.
The point is that they are already re-encoding videos, so they can just switch to re-encoding to webm instead.
Good thing webm is a separate project that’s only sponsored by Google, then. Also, you didn’t even address the fact that Google is a major content provider when it comes to video.
How on earth is that relevant? The requirement for an open web doesn’t disappear just because most people don’t know or care.
[q
Actually, that is exactly what it means. Look up the patent policy at w3.org.
[/q]
irrelevant. It can exist on the web and be closed, otherwise flash would be incompatible. I don’t like flash but it is part of the web.
Ok WebM as a container is sponsored by Google, but WebM uses the VP8 codec, that was developed by On2 which Google purchased the company. So it is more then a sponsor they owned it and then released it to be open. I could care less if Google is a large content provider, that is why I didn’t comment on that. I was referring to OTHER companies, not Google.
Oh, I see. Again most people don’t know the web is supposed to be OPEN. It is not completely open as long as there are closed parts of it. And that was my point, who cares as long is the consumer gets a good experience.
You obviously don’t get what I am saying and I am too tired to try to explain so I am done with this.
Thank GOD…
And just who are you? I have seen plenty of your debates, so you can hardly say a thing. Go Troll somewhere else because that is what you are doing with that comment.
No, I’m thanking a nebulous concept.
I thought you were done here… or was that just an empty promise?
I never said it can’t exist. I said it’s incompatible with an open web.
VP8 was released as part of WebM.
The point is that the fundamental building blocks need to be open.
I advocate all positions sustained by OSAlert and back the decision from Google.
Nonetheless: It shows once more that the H264 patents should be invalidated.
It is clear that from a licensing point of view, we should all support WebM. The 10 questions here show it in a perfect way. It has also been shown that H264 is superior. And it is a fact that it is very widely spread.
We’re facing the problem that we’ll have to use twice the storage, and a LOT of energy (think YouTube) to transcode the existing H264 content to WebM/Theora. This can’t be true! Someone has to stop those crazy patent trolls. Actually I hope Google’s WebM announcement is just one move in this direction.
A web developer
No, it hasn’t.
It certainly is a claim that is widely spread.
YouTube content has already been transcoded to webM (not Theora). WebM was announced in may 2010, and in November it had reached 80% of YouTube content converted to WebM:
http://www.osnews.com/story/24021/WebM_Update_80_of_Daily_YouTube_V…
It is probaly nearing one hundred percent by now.
Google has a million servers, which are on all of the time. The conversion to WebM was done using spare capacity of Googles servers (idle time). Since the servers were on anyway, this required no more energy than if the conversions had not been done.
Edited 2011-01-13 05:03 UTC
… why do you even care?
Read the whole post but seriously:
Boho, I don’t want WebM instead of H.264 -> Safari only supports H.264 and Apple has been pro H.264 the whole time and encode lots in it.
Boho why aren’t you consistent and go after flash to? -> Apple iPhone don’t have flash, boho, why don’t you help Apple?
Yeah, lots are encoded in H.264, it’s an issue for direct upload. But if we would keep the same formats forever we’d be using wave/iff/bmp/..
WebM may be open source, but that doesn’t mean Google doesn’t control it.
If Google are really serious about this openness thing, they should set up an organization so many different companies can work together on WebM, or maybe donate it to W3C or another standards body. Right now, despite being OSS, Google de-facto controls WebM. And although it is certainly bad that h264 is patented and all that, it is at least controlled by more than one company.
That being said, I definitely consider WebM to be the lesser of two evils.
Google have provided (donated) a worldwide, perpetual, irrevocable, zero-charge, royalty-free license to everybody with respect to WebM.
http://www.webmproject.org/license/bitstream/
The code is open source, and the development process is accessible to all.
http://www.webmproject.org/code/contribute/
So Google already have “set up an organization so many different companies can work together on WebM”. exactly has been happening now for over six months. here are the organisations already involved:
http://www.webmproject.org/about/supporters/
I can’t see how WebM could possibly be any more inclusive. You need to actually come up with something that Google haven’t done to make WebM open before you can begin to criticise them for not doing enough.
Awesome.
I’m trying to find information on if WebM organisation (if there is one) is simply sponsored by Google, or also controlled by Google.
If it is only sponsored by Google, and control of it is democratic in similar fashion to how open web standards are developed, color me a believer. (Which does seem to be case.)
Edited 2011-01-13 11:34 UTC
They can change the licensing in the future but not for what has already been released. What is currently available under the BSD license remains open to all and would become the starting point if it really came down to forking the code away from Google’s control.
Though not BSD, MySQL is a good example; when the decisions of it’s steward came into question, the source was forked into a new database project – by the original MySQL developer no less. More recently, the OpenOffice project; Oracle’s stewardship of it since the Sun purchase has driven developers to fork the code starting the LibreOffice project.
Forking a project is not promoted as a first response but it is an option when no other remains.
The is the best analysis I have come across of the commercial, financial and strategic background and implications of Google’s move. Warning to Googletards – you won’t like it.
http://arstechnica.com/web/news/2011/01/googles-dropping-h264-from-…
You, sir, are an idiot who doesn’t read osnews and just came to troll:
http://www.osnews.com/comments/24252
And you think Peter Bright’s analysis is the best, believing his shameless, mind-boggling, orwellian spin that H264 is open and VP8 is proprietary. You, indeed, are an idiot.
I couldn’t give a shit, frankly. What WebM is really about is Google being afraid of being held over a barrel with YouTube if the content on there was to be largely raw h.264. Good for them. I would be.
The rest of us getting a genuinely free format, with working code no less, that can be implemented freely into any operating system, software or any new device that comes on the market without the say-so of an organisation of trolls (or indeed Google) who would rather others were kept out.
What an idiotic article.
Nice rhetoric. There is no “apparently” about it.
Oh I see. That old trick! Yes, and OpenVMS, OpenWindows and OpenServer are open because they have open in the name.
LOL
I hope the author doesn’t describe Java or C# as Open. Or Mozilla. Or OpenOffice/LibreOffice. Or all those other Open Source projects that started off as commercial products.
What is now shall ever be.
*golf clap* Took him half a page. What a clever boy.
Yes, and has been pointed about eleventy billion times:
a) It is equally likely that H.264 infringes on patents filed by On2 and held by Google.
b) MPEG-LA have had ten years to sue On2 and never have. Google purchasing On2 doesn’t suddenly make patents appear at MPEG-LA.
He’s right you know. Let’s stop with all this silly “open web” nonsense. What has openness and transparency ever done for the Internet?
I’m just going to stop. The article is hilarious, doubly so because the author actually appears to believe what he is writing.
Follow-up on OSAlert : http://www.osnews.com/story/24259/Microsoft_Opera_s_Haavard_Respond…
Edited 2011-01-13 21:15 UTC
This is a lesson we have learned from Flash, when a proprietary software is getting popular and becomes a defacto standard for www, it is harmful to everyone. Because the proprietary software will control the world, if they hate somebody, the will not support the platform, and people on the platform then have trouble to live with Internet.
Edited 2011-01-14 07:34 UTC
Now, now.
Let’s not overload “proprietary”.
h264 is ‘encumbered’, ‘patented’, ‘evil’.
It’s not even ‘software’.
It’s a ‘standard’ with many strings attached. Strings which wrap may around your neck if you use the web or have a business or ever consider making money from anything you do.
Yet mencoder, x264 et al are free software.