| |||||||||||||
Did you actually read the article?Did you actually read the article?Posted Mar 15, 2012 22:41 UTC (Thu) by rqosa (subscriber, #24136)In reply to: Did you actually read the article? by rqosa Parent article: Idealism vs. pragmatism: Mozilla debates supporting H.264 video playback (ars technica)
Oh, and one more reason: 6. GStreamer is supposed to support multiple platforms, including Windows and MacOS X; so, adopting GStreamer could reduce the amount of platform-specific special case code in Gecko Also, about the redundant network stack: I believe that the same situation is present in KDE; it has its own HTTP client library in KIO, but (IIUC) Phonon-based media players using the GStreamer Phonon backend will use GStreamer's HTTP client implementation instead of KIO's one when playing an Icecast stream, and similarly Konqueror and other QtWebKit-based browsers for KDE will use GStreamer's HTTP implementation when playing HTML5 video. However, one could say that that redundancy still exists even in the case that Firefox / XULRunner / Gecko isn't using GStreamer, because most desktop/notebook Linux installations now (excluding Android) will have both Firefox and GStreamer present.
(Log in to post comments)
|
|||||||||||||