Mike Shaver

You don't remember what the original argumentation was. Firefox is free, Mozilla can't afford the patent licensing, that's all. This is still entirely true (note that "afford" in the above should be read in the "free license" context, not monetary). For the same reason, Chromium has no H264 support. Patented codecs don't mix well with free software. They took a stance here based on their philosophy, that much should have been obvious. The reasons not to do it with system codecs before are enumerated here: http://shaver.off.net/diary/2010/01/23/html5-video-and-codecs/ Most of them still apply, but are simply less important 2 years later. The Windows XP thing was even brought up in the original discussion thread. put the user back in the stone age of the internet I would say that's essentially what the current patent legislation is doing. Worth fighting against.

Well, I still call bullshit. Especially if this is the best you can come up with. Let's see: http://shaver.off.net/diary/2010/01/23/html5-video-and-codecs/ We have exactly two references to "security" : And I want that not only altruistically, but also because I want the crazy awesome video (animation, peer-to-peer, *security*, etc.) ideas that will come from having more people, with more perspectives, fully participating in the internet. and (about 60% of our users are on Windows XP, which provides no H.264 codec), *to security* (exposure of arbitrary codecs to hostile content), and to user experience None of them even slightly imply that the Mozilla team thinks H.264 is insecure. http://weblogs.mozillazine.org/roc/archives/2010/01/video_freedom_a.ht… This is an FAQ or rant if you will, which goes on and on about why Mozilla does not want to implement H.264. Oh yes, not one single word about security This one: http://weblogs.mozillazine.org/roc/archives/2009/06/directshow_and.htm… indeed discusses security. It is however not geared towards H.264, but towards Microsoft's DirectShow. Using this article as a reference regarding Mozilla's stand on security on H.264 is at best a stretch and at worst intellectually dishonest. I'm calling "do your homework, lest you look like a badly-informed fanboy". I never thought of myself as a fanboy, but be my guest to dive into ad-hominem, when you're out of arguments. In addition. I'm rather an uninformed fanboy then…

Sigh! When did the Mozilla ever claim that they do not ship H.264 because it's insecure? Mike Shaver and Robert O'Callahan both -- during the early attempt to frantically spin this as more than just an ideological PR stunt -- pointed to security as a reason why they didn't feel comfortable delegating to other software. See the following posts: http://shaver.off.net/diary/2010/01/23/html5-video-and-codecs/ http://weblogs.mozillazine.org/roc/archives/2010/01/video_freedom_a.ht… http://weblogs.mozillazine.org/roc/archives/2009/06/directshow_and.htm… Of course, they did eventually come clean and admit this was just a naked ideological PR stunt. O'Callahan's quote about the fact that delegating to OS codecs would mean giving up Mozilla's control -- sorry, "leverage" -- over what users can do with their own computers is particularly telling, especially in a debate that's ostensibly about "freedom". I'm calling bullshit, badly disguised as a strawman. I'm calling "do your homework, lest you look like a badly-informed fanboy".

Looks like Firefox 3¹, all the way back in 2008! There is a good description of fixes and workarounds on LWN². ¹ http://shaver.off.net/diary/2008/05/25/fsyncers-and-curveballs/ ² https://lwn.net/Articles/328363/

I don't like databases, and the reason I don't like them is that they seem to cause terrible performance problems in web browsers. Firefox's use of SQLite is well known to cause or have caused trouble - for example http://shaver.off.net/diary/2008/05/25/fsyncers-and-curveballs/ . And then you get advice like this: http://savanne.be/153-performance-tip-of-the-day/ . Safari has similar issues. In particular the favicon SQLite database is a common source of slowness - see http://www.chriswrites.com/2012/05/how-to-delete-favicon-caches-from-s… I don't know if these are inappropriate uses of databases, or if these databases could perform well, but are misconfigured in some way. But I have seen SQLite cause performance problems on desktop apps so often that I think there must be something hard about it, that's not hard about other data storage mechanisms.

I got schooled angrily by the creator of JavaScript and founder of Mozilla on the difficulties of NaCl and Dart here http://shaver.off.net/diary/2011/10/28/approaches-to-performance/comme… He says it would be impractical for other browser vendors to keep up with the sprawling mess of APIs required by NaCl known as Pepper. Also Google's behavior around it's open source but not open standard tech like NaCl and Dart leaves a bad taste.

In Mozilla's defense, they've handled Places-related issues well in the past. http://shaver.off.net/diary/2008/05/25/fsyncers-and-curveballs/

Looks like Mike is going to Facebook. http://shaver.off.net/diary/2011/10/01/whats-next/

To be clear, it was one Mozilla employee (a product manager, not an executive) whose blog comments were quoted by the tech press and misinterpreted as speaking for Mozilla as a whole. Not everyone here at Mozilla is as blunt as Asa, and not everyone agrees with him. For example, see this thoughtful and detailed response by Mozilla VP Mike Shaver: http://shaver.off.net/diary/2011/06/28/enterprise/

Mozilla has said [0] that they could pay the $5M/year but they won't because 1) it means content producers have to pay money to obtain licenses and more importantly 2) other people cannot create mozilla forks without licensing h264 themselves. [0] http://shaver.off.net/diary/2010/01/23/html5-video-and-codecs/

This is from October 2009 (yes, more than a year ago), when Mozilla blocked two .NET-related plugins because of a security flaw (with Microsoft's blessing, no less). As far as I know, both plugins were both unblocked within a week or so. See http://shaver.off.net/diary/2009/10/19/update-on-the-net-framework-ass… for more information on what happened.

I imagine I'm missing something. But why couldn't Mozilla use an extension that supports H264? Similar to Ubuntu's nonfree packages? I imagine the HTML5 video tags are pretty deep in Gecko, but surely they could 'pave the way' with a clear interface for such an extension. And then use one that is developed by others. Isn't that one of the advantages of having a standardized <video> tag? Reading this: http://shaver.off.net/diary/2010/01/23/html5-video-and-codecs/ It sounds like Mozilla is worried about (a) encouraging a non-free web and (b) passing on licensing fees to other people who use their product downstream. But surely there is less risk in being 'side-stream' so to speak with licensed technologies, esp. under a standardized markup. Anyway, curious legal issue.

Ugh. Please, read the other side of the "argument", I was going to say "research", but seriously, the information is 5 seconds of google-fu away: http://shaver.off.net/diary/2010/01/23/html5-video-and-codecs/

3 days old, Mozilla has already blocked and unblocked the add-ons in question. http://blog.mozilla.com/security/2009/10/16/net-framework-assistant-bl… http://shaver.off.net/diary/2009/10/18/update-net-framework-assistant-…

> Acid 3 came way too late for the gecko version being used. Opera and WebKit aced it two months ago. Gecko had plenty of time. One of the Mozilla guys explained here the Firefox approach to Acid 3: http://shaver.off.net/diary/2008/03/27/the-missed-opportunity-of-acid-… In the end, though, it comes across as a poor excuse.

The article glosses over the fact that fsync() itself has major issues. For example, on ext3, if you call fsync() on a single file, all file system cached data is written to disk, leading to an extreme slowdown. This led to a Firefox bug, when the sqlite db used for the awesome bar and for bookmarks called fsync() and slowed everything down. http://shaver.off.net/diary/2008/05/25/fsyncers-and-curveballs/ OS X does a fake fsync() if you call it with the defaults. https://developer.apple.com/library/mac/#documentation/Cocoa/Conceptua… fsync in Mac OS X: Since in Mac OS X the fsync command does not make the guarantee that bytes are written, SQLite sends a F_FULLFSYNC request to the kernel to ensures that the bytes are actually written through to the drive platter. This causes the kernel to flush all buffers to the drives and causes the drives to flush their track caches. Without this, there is a significantly large window of time within which data will reside in volatile memory—and in the event of system failure you risk data corruption

I generally like Gruber and think he tends to weigh his thoughts and arguments very well - but I still can't forgive him for buying MPEG LA's PR release[1] hook and sink[2]. Since when has it been a good idea to take a press release at face value[3]? He hasn't recanted this complete acquiescence, so I am under the impression that he sincerely believes them - and only on the grounds of that single release. Maybe he was biased, too cute for his own good, had a brain fart, or is too stubborn to accede. I really don't know, but this is one case where I can't really blame Gruber haters for framing his writing and philosophy in a certain way. [1]: http://www.businesswire.com/news/home/20100825006629/en [2]: http://daringfireball.net/linked/2010/08/26/h264 [3]: http://shaver.off.net/diary/2010/08/27/free-as-in-smokescreen/ (Fixed a typo: "thought" to "thoughts". Don't read anything into it!)

"The burden of what? Deciding what video content is acceptable? Like I said before, that should not be Mozilla's role, but it's the one they've taken on." The burden of dealing with patent encumbered formats. Someone would have to pay or it would remain illegal. As Firefox developers develop Firefox, they have their say in what do or don't do Firefox. And even if they pay it wouldn't be free since there would be strings attached. "Yes...and? What's your point?" My point is simple and has remained the same from the very beginning: h.264 is not compatible with an open and free (as in freedom) internet. Therefore implementing h.264 is either not compatible with free software, not an issue in countries where software patents don't exists, or done in an illegal manner. So here we go again: How much would someone value his freedom? This guy explains it in much better terms than I could: http://shaver.off.net/diary/2010/01/23/html5-video-and-codecs/