On that grounds, how will Firefox browser be treated in future if they were to implement the DRM/EME extensions?Įven if the extensions could be made optional and disabled, their very existence in Debian OS will go totally against several of the DFSG (Debian Free Software Guidelines):Ģ. Even firmware that is critical part of a laptop (like touchpad and graphics drivers, etc.) is shunned aside from the repo if they find it to be not freedom friendly. If you really want speed I suggest looking into the daily mozilla PPA instead of these custom builds.Debian is the strictest of projects when it comes to adhering to FOSS standards. Actual code difference makes much more impact than the several percents of performance you can squeeze out by compilation flags. JM+TM is now 'officially' faster than both Webkitcore and V8 on Sunspider now. With all that said, the fact is that the most performance you will increase is with the JM+TM that is still brewing in Firefox 4 nightlies. PGO, on the other hand, might do a bit more. The main advantages of building for custom processors is the enabling of extra instruction sets - most of which benefit floating point stuff, and not really that much relevant to the web browsing things that Firefox does. The diff that, for example, Swiftfox supplies lists only common configurations such as enabling pipelining and increasing the max per domain connections.

Simply because there's an '-O3' and a 'march=prescott' CFLAG won't really do THAT much of a difference.

Honestly, the difference in these such re-branded custom builds are minimal at best. Is it faster then Swiftfox and other variants?

Pale moon browser eme drm sandbox