Re:Google Chrome's H.264 support not true "free" software
by zokier on Friday January 22, 2010 @08:07PM
(#1071144)
So using Flash/WMP/QT -plugin to playback video via <object>/<embed> -tags is OK but using native APIs to play <video> -tags is insecure and buggy. Riiight.
Re:Google Chrome's H.264 support not true "free" software
by natmaster on Friday January 22, 2010 @08:26PM
(#1071165)
"Mozilla wants to encourage Web authors to use Theora"
That seems to be working so well. Really they're just encouraging users to not use Firefox. The user chose to have those codecs on their system - either by installing and OS that comes with it, or installing the codec itself.
Let the user chose what codecs they want to support.
Re:Google Chrome's H.264 support not true "free" software
by alain94040 on Friday January 22, 2010 @07:31PM
(#1071088)
Firefox won't use system codecs because they might be insecure, they might be buggy
This does not address the original objection. Calls to the Mac and Windows are not known to be any less buggy or insecure than calls to the h264 APIs. So why accept one and not the other? The only sane answer of course is that you can't build an app at all without calling the OS basic APIs of your host machine, but you can try to have an ugly work around h264.
Firefox won't use system codecs because they might be insecure, they might be buggy, and Mozilla wants to encourage Web authors to use Theora.