I am not against the use of arm in personal computers, desktop and laptops, before I accepted to pay dearly for a mac, mainly, because it had an i7 core inside. They are switching to arm, because their software is very well developed, there are very good video, image and audio manipulation applications for ipad and iphone, they will rely on that to make the transition. ![]() I believe that all this transition is because manufacturing ipads is cheaper than making macbooks, so they will manufacture ipads in the form of a notebook, call them a macbook, and increase the profit margin with that.Īpple's arm processors look quite powerful because they are compared to other arm and other low-power x86 processors, but I think it will be a distress for people who need to do some heavy lifting. I believe that they would have made a better choice with power, or even with AMD. ![]() My opinion is a move to profit, as there is currently a "hypie" on top of the arm. While I do intend to continue supporting TenFourFox for those occasions I need to use a Power Mac, this Talos II is undeniably my daily driver, and fixing bugs in the mainline Firefox build I use every day is unavoidably a higher priority.Not that I don’t love ARM, I love ARM, I love my raspberry and the projects I did with them, but I mean I don’t think Apple will really improve the arm, as it is a competitor of the Intel Core i7 and amd ryzen. I don't have any easy means of cross-building TenFourFox on the Talos II (which, by the way, with dual 4-core CPUs for 32 threads builds Firefox in about half an hour), so I need to figure out how to balance this additional time requirement with the time I personally have available. Although the build and test process is about 2/3rds automated, it still needs intervention if it goes awry plus, uploading to SourceForge is currently a manual process, and of course the documentation doesn't write itself. ![]() Build day on the G5 is, in fact, literally a day or sometimes close to two (with the G5 in Reduced performance to cut down on fan noise and power consumption it takes about 20 hours to generate all four CPU-optimized releases, plus another 6 hours to regenerate the debug build for development testing if there are JavaScript changes, I usually kick off a round each on the debug, G4/7450 and G5 builds through the 20,000+ item test suite and this adds another ten hours). In a related vein, the recent shift to a 4-week cadence for future Firefox releases starting in January will unfortunately increase my workload and may change how I choose to roll out additional features generally. I have not decided what to land on TenFourFox FPR17 mostly because this fix took up a fair bit of time it's possible FPR17 may be a security-only stopgap release. Since this is syndicated on Planet Mozilla let me give a big thanks to Ted Campbell for figuring out the root cause, which turned out to be a long-standing problem I don't think anyone ever noticed before. ![]() The problem never affected OS X Firefox for Power Macs because those builds were only ever 32-bit, and even TenFourFox is 32-bit through and through even on the G5 largely for reasons of Carbon compatibility which we need for some pieces of the widget code. for your G5, you may want to check out this Talospace article for an upcoming low-level fix especially as we need to ensure big-endian systems work fine with it. If you build Firefox on 64-bit Linux, *BSD, etc.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |