Dear MSFT and AAPL, Embrace Theora!

I swear; I’m not a hypocrite. I 100% stand by what I wrote to Mozilla about supporting H.264 or risking killing video on the Web sans plugins. I also continue to believe that H.264 is a significantly superior codec to Theora (it’s a fact so it’s hard to deny). And I also continue to believe that publishers with huge libraries of H.264 encoded video don’t want to go through the process of re-encoding all that video; not to mention the added expense of storing and distributing multiple formats. Mozilla, I say to you again: you need to support H.264 video (be it natively or through system libraries such as Quicktime or Gstreamer).  The Web needs H.264 to be universally available because the largest content producers need the highest quality codec to distribute their video to everyone; they need a codec with broad hardware support such that mobile devices don’t run themselves dead in 5 minutes of video playback. For now, and for the foreseeable future, H.264 is that codec.

Perhaps the greatest misunderstanding of my previous article was that I was somehow saying that Mozilla should drop support for Theora. Despite the number of times I refuted this claim, it seemed to persist. For the record, I do not think Mozilla should drop support for Theora in Firefox; I think they should add support for H.264 .

The Pareto Principle, if you subscribe to it, tells us that 80% of video content is going to be generated by 20% of the market. That 20% simply won’t settle for an inferior codec in the interest of that codec being free. For all of Mozilla’s posturing and idealism, the only real outcome they can achieve is that some 80% of the most viewed online video content will continue to be delivered via Flash, Silverlight, or some other plugin. Of course, that leaves us with all the video content that other 80% of content producers generate; and that’s where Theora comes in.

It’s All About the Tail!

The Web has given everyone a voice (I certainly could never have written an article that was read by over 10,000 people in less than 24 hours without the Web). The Long Tail Phenomenon a truly wonderful and powerful force; independent content producers now have the ability to distribute their content to a huge audience. The aspiring filmmaker can post his video on the Web; the aspiring musician can post her music on the Web. Bloggers are treated more and more like first-class journalists every day. And the potential for exposure is certainly far beyond what could have been achieved independently even 10 years ago.

But members of the Long Tail have very different needs and expectations for their content than the major content providers. For starters, the aspiring filmmaker probably doesn’t have the $10,000 per year royalties that could (theoretically) be due for his video encoded in H.264 and distributed on the Web. He also likely doesn’t have a lawyer to help him understand the obscure patent laws that cover H.264 usage. And he certainly doesn’t have the resources to fight the potential legal battle if he’s found to (even accidentally) misuse his “rights” to H.264.

This niche is where free formats demonstrate their great value; and speaking for the likely thousands of these hopeful filmmakers out there, we need a format that we can be confident will always be free. We need a format that we are free to do whatever we want with. We need a format that enables everyone to create their content and share it with the world freed from any legal concerns. For now, and for the foreseeable future, Theora is that codec.

No, the quality’s not nearly as good; but it’ll work for the guy just trying to get his film out there (Conversely, it definitely won’t work for FOX for putting HD episodes of 24 and House online). The point is, for people in the Long Tail, sometimes “good enough” really is good enough.

Microsoft and Apple Agree?

These guys are never on the same page so this must be big! Neither Microsoft or Apple are supporting Theora in their browsers. My thought is: Apple? Really? “Best friend” of the Indie Producer? A company that has built a reputation for providing fantastic support for creative professionals in both the audio and video industry should know better! As for Microsoft; well, nothing that company screws up surprises me, honestly.  There’s simply no excuse for not supporting Theora (on the desktop; Mobile is a different matter altogether due to the aformentioned availability of hardware decoders for H.264). The code is out there; there are implementations for every major OS. There’s nothing preventing either company from supporting it other than their own stubbornness; very much like Mozilla’s own stubbornness regarding H.264.

It’s About Producer Choice

This isn’t about consumer choice; it’s very clear that consumers just don’t care. It’s about choice for the content producers. It’s about letting the guy who maxxed out 10 credit cards to scrape together a movie (and unlike Kevin Smith, got rejected by Sundance) get his film on the Web for the world to see knowing that he’s not in danger of racking up even more debt.  It’s about embracing the long tail; the Here Comes Everybody mentality.

The Web needs H.264. The major broadcast and cable TV networks and the other big names of content will never choose Theora (I reiterate, they’d rather deliver their video via Flash to take advantage of H.264 than use Theora). For HTML5 video to succeed Firefox must support H.264.

Microsoft and Apple, it’s time for you two both to ensure that the independent content producers of the world get equal treatment in your browsers. I applaud you for accepting H.264 so that we could all get our favorite TV shows and movies online without plugins. Now I’m asking you to make sure we can also get content from smaller sources like The Guild and Red vs. Blue. For the Long Tail to continue to grow as a source of meaningful and influential content, we also need free video; and for that, we need Theora.

  

Webkit vs. Firefox on H264

I posted this as a comment on another thread; but I thought it warranted its own post.

Webkit is an open source project.
Webkit development is sponsored by corporations (Apple and Google primarily).
Webkit includes support for h264 video.

Firefox is an open source project.
Firefox development is sponsored by corporations (Mozilla Corporation primarily).
Firefox does not include support for h264 video.

…and yes, the webkit you can download from webkit.org includes h264 support. If Mozilla “can’t” include H264 in Firefox which has been one of the primary arguments by commenters; I’m failing to see a reason.

  

Dear Mozilla, Please Don’t Kill HTML5 Video!

Mozilla and I have a long and not-so-storied history together. I first began running what was at the time called the Mozilla App Suite with the “Milestone 10” release in October 1999. I was (I believe) one of the first people outside of the core team to build (as in compile) the browser that would come to be known as Firefox. It was called Phoenix at the time and the team hadn’t released any binaries. I remember talking to the core team  on IRC getting instructions as to what build flags to add to build Phoenix rather than the app suite. For a time, I released unofficial nightly versions of Phoenix (then Firebird) compiled with Xft support for anti-aliasing on Linux that were distributed through MozillaZine. Long story short: I’ve contributed only slightly to the project; but I’ve supported it as long as anyone and generally my ideals match up nicely with the Mozilla team.

Until now.

I’m a huge supporter of open formats; I always have been. One of the main reasons Microsoft was able to rise to its Monopoly-level dominance was the proliferation of the proprietary MS Office file formats. However, I have reason to believe that Mozilla’s decision not to support H.264 encoded video via the HTML5 video tag due to the “patent encumbrance” of the codec, is a wrong decision and one that, unless they change their mind, will kill any hope of ushering a new era of online video distribution that exists without plugins. Mozilla has always been an organization willing to take a stand for what they believe in; and they believe in the open web.

Three of Four

With Microsoft announcing support for H.264 video in IE9, three of the four “big name” browsers will be supporting H.264 video. Truthfully, this move surprised me when it was first announced; I had assumed, like others, that Microsoft would choose only to support their own proprietary format. The success of Office taught the team in Redmond that simply using proprietary formats isn’t good enough; you have to completely own the format. However, without support from Mozilla, H.264 can never be the “encode once, deploy anywhere” format that people and businesses need it to be.

Encoding is slow and expensive

Video encoding is a very processor-intensive process; it’s time consuming, expensive, and the resulting files are large which lead to bandwidth and storage costs. The current Flash implementations on the web are already H.264 capable, and much of the video content for the web is already encoded in H.264. It’s nothing but an expense to create and maintain additional encodings. And even if we as web developers can create a robust fallback system that prevents the user-experience of online video from regressing to the days of “choose your format,” the added costs are something most companies simply cannot ignore.

Theora Sucks

I say that harboring no ill-will towards the very talented engineers who have sunk countless hours of their time into Theora. But as numerous comparisons have shown, it simply can’t keep up with H.264 in terms of quality; especially at low bitrates. MPEG2 was once considered great; but in the face of the current top-dog codec, it (like Theora) sucks. People and businesses are willing to embrace free software when it provides an equal or better product than the proprietary alternatives (see the success of Linux on the server). However, when free software doesn’t keep up with the best non-free products, people stay away (see the lack of success of Linux on the desktop). Simply put, there just aren’t that many people who share the same moral imperative as the Free Software Foundation; most of just want it to work.

There’s a Precedent Too

Mozilla has a track record of not sharing the stance of “nothing proprietary,” which implies that as an organization, Mozilla is willing to pick it’s battles. If it wasn’t, it wouldn’t allow proprietary plugins like Flash. Imagine also if Mozilla had taken the same stance against GIF images in the early 2000′s when the format was patent-encumbered just as H.264 is today; the browser barely would have gotten off the ground. In that instance, pragmatism and the need to not break the web won out over a desire to only support free and open formats.

Don’t Break the Web

Team Mozilla: I understand your desire to show support for free and open formats and I empathize with your belief that the best way to advance the web is to truly embrace those formats. But I wish this fight was one in which you’d lay down your sword. I disagree that “being idealists” is your reason for being. I believe that your first responsibility as a browser vendor is to make the web a better place; it’s certainly what you’ve strived to do since your inception. But honestly, from the view of a realist, the only thing you’re going to accomplish is making the HTML5 <video> tag unusable.

Two Proprietary formats

What’s worse, you’ll force people to continue to use Flash as the preferred delivery platform for video on the web (which, as covered above, already uses H.264 for video). Instead of one proprietary format, people will now be forced to use two simply because of your refusal to accept that sometimes you have to take a few small steps to get to your goal. I hope you can at least agree that going from two proprietary formats to one is a marked improvement.

Please…

…don’t do this to one of the most exciting and promising technologies being delivered in HTML5. You’re voluntarily creating another format war and the only result of format wars is people avoid both alternatives because it’s too much work to support both. Help us continue to make the Web a better place and move it forward one step at a time; even if those steps aren’t quite as long as you’d hoped they’d be.

Update (8:20 am EDT)

I’ve created a response post that addresses some of the points in the comments titled Mozilla’s Not Non-Profit (and Other Thoughts). Thanks to everyone who read this and considered its content and has an opinion to share. Disagreement builds great conversation!

Update (March 22)

I’ve written a follow-up piece about browsers supporting Theora and my belief that despite the its shortcomings, it has a real place in the future of the Web. Please check out Dear MSFT and AAPL, Embrace Theora!