Moreover, with the exception of the JIT, which I'm trying to work on between TenFourFox, Christmas holidays and visiting family, Firefox exists and works and can be built. Mozilla has proven willing to support platforms outside their core as long as those platforms take responsibility and the support for those platforms doesn't interfere with tier-1 builds. The irony with the current big-endian issues is that they're actually with Skia, which was written by. They've taken some of mine, and they've even taken patches to fix big-endian PowerPC and PPC64. ( Too bad Google doesn't seem to.) Mozilla, on the other hand, has been willing to accept PowerPC patches even after PPC OS X was no longer a tier-1 platform (which is where TenFourFox came from), and is taking patches to repair Firefox builds on ppc64le today. We've seen that with Intel's stagnation on x86, we saw that with Internet Explorer 6, and we're about to see it again if Chromium is successful in driving Gecko's marketshare to irrelevancy.Ĭhromium on POWER9 exists, and apparently works I won't use it personally for the reasons I cited above, but I salute the work that went into it. If you're using a Talos II as I am, you of all people should recognize the vulnerabilities of an architectural monoculture.
This potentially allows Chromium to arrogate even more browsershare to itself, enabling Google to continue with eroding support for anything that isn't Chrome. There's more about that on our sister blog, TenFourFox Development.
#TENFOURFOX 2018 RELEASE WINDOWS 10#
Today's news is that apparently EdgeHTML, the layout engine for the Edge browser, is being replaced not just on mobile, not just for ARM on Windows, but even on Windows 10 itself - with Chromium.
0 kommentar(er)
