Bad, Bad, BAD! (Firefox is basically ditching html5 video support)
GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Why is this bad? Firefox can't use h.264 because of licensing issues, so they really can't do anything about it. That's why they're focusing on Ogg/Theora. If Google comes through and opens up VP8, they can support that.
It would be great if browsers that supported html5 video tags would just use whatever codecs were available on the os. That way people could just use whatever they wanted. h.264 be damned.
And all Google has to do is move YouTube to VP8. I'm sure they're looking at doing that, and once it happens, h.264 is likely going to be an also-ran. Unless Jobs follows through on his FUD about infringements on h.264 patents in which case we all get to watch the lawyers get richer. Again.
I've already had a good rant relating to this here.
But I have another concern. These ideas of using javascript and canvas and whatnot to do fancy stuff are all well and good if the user has a fast enough computer. To my knowledge there's no standardised way to let websites advertised system requirements. Are we going to get further into a situation where the web sleepwalks into demanding more and more powerful machines to run sites with worse and worse bloat, just like commercial software developers have done with desktop apps. Consequentially to that, we end up with a "two tier" web, where sites carrying unnecessary bloat along with useful information are inaccessible to the poor and those in the developing world. (I mean, what's the POINT of canvas? It seems to me it does everything SVG does, but worse). And while with desktop applications people can and do keep using older versions (even past end of security fixes, not that that's a good option), people don't have that option with websites.
smeeze*;
As a long standing member and "guru in training", you know that we frown on bad thread titles. The irony here is that your title for this one says it all!!!
For some reason Mozilla chose to include their own codec rather than supporting OS codecs through gstreamer, directshow, etc. This means you can't even license your own H.264 codec for personal use (or use the one included Windows and OSX) and use it with Firefox. I don't know if there's a plan to support OS codecs nor why it was decided not to.
That pretty much says it all...it means that you couldn't use H.264 (or any other codec for that matter) with FF, because there simply would be no support at all.
I agree that this whole H.264 patent business is getting way out of hand.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.