Linked by Thom Holwerda on Sun 16th May 2010 12:52 UTC, submitted by mrsteveman1
Internet & Networking Mozilla, sticking to its ideals of the open web, decided long ago that support for the patent-encumbered H264 codec would not be included in any of its products. Not only is H264 wholly incompatible with the open web and Free software, it is also incredibly expensive. Mozilla could use one of the open source implementations, but those are not licensed, and the MPEG-LA has been quite clear in that it will sue those who encode or decode H264 content without a license. Software patents, however, are only valid in some parts of the world, so an enterprising developer has started a project that was sure to come eventually: Firefox builds with H264 support.
Permalink for comment 424878
To read all comments associated with this story, please click here.
Member since:

"To re-iterate: If you use the built in functionality of the OS, you are not violating any patent!, you re-use existing functionality, less code to maintain.

Eh, no. More code to maintain.

Code to make use of DirectShow (XP/Vista/7), but since DirectShow is currently being phased out, you need code to support its successor too (Media Foundation). Then you need code to support QuickTime. Then you need code to support Gstreamer (and hope the user has H264 codecs installed on his system, not a given in Linux land).

So, more code.

Easier then (in Linux land, at least) to use the decoder embedded into the video card. Two advantages: (1) it is legal on Linux (since the video card is paid for, everyone has an implied license to use it), and (2) you get hardware-accelerated decoding.

Mozilla itself could ship (as open source) a browser that used video decoders embedded within the system's video card hardware (if there is any). No need for forks and clones.

Downside: Doing this just encourages h.264 on the web, which is not in the best interests of the vast, vast majority of people.

Edited 2010-05-16 13:54 UTC

Reply Parent Score: 6