He has a number of Macs, only one of which is allowed to run the latest version of Mac OS X, and nonetheless he refuses to move any of his other systems past 10.6.x. I was just recently talking to an old, dear friend of mine. I don't know the extent to which Apple has an impact on GNU+Linux, but I do know they changed around the architecture a bit and support for things such that Google and Mozilla have had to recompile their browsers and, as far as I know, they no longer support older versions of Mac OS X, so it would be my guess they are finding less and less reason to bother making 32 bit versions of their software overall, and not just with respect to our preferred platform. However, Firefox has definitely improved and, having made the in-good-faith experimental migration to it, I haven't moved back to Chrome (or even to Chromium).Īs for 32 bit abandonment, I don't think there's any credible argument to be made that it isn't coming, though exactly how and when can, I think, be debated. I had previously tried to use it in lieu of Chrome, but it seemed like there were always things I didn't like, or other, niggling little issues. I don't use Chrome any longer, and haven't in probably the better part of a year. Note: I'm only considering my computer in this post.
Is firefox for mac 32bit or 64bit update#
I can try to update but have to timeshift back to that day before six month ago because arch will not run anymore with my old configs and only God knows how many i have lingering in my rootįirefox is the same way, i stay away from it, they hide useful tweaks and is more like a closed source now instead of having the freedom you believe you have. all my old conf files i had personalized are now in conflict with the new arch way.
in arch linux after unplugging my pc for six month i could not get it back running with the new updates. i finally gave up on firefox as i did with arch linux. Quite too many times i had to redo all my about:config tweaks which would have more issues with every firefox update. I do not think that spending more time on the crashes will be worth the time, unless the same Firefox 32-bit should decide to crash, even though the profiles have been created from scratch now. Yet, I assume this will remain one of the many unexplained riddles in life. This does, however, not explain why Firefox 69 32-bit was effected, but Firefox 69 64-bit was not. So chances are that the crashes which happened here were really caused by outdated information in the old profiles. After having permitted Firefox 69.0.1 32-bit to create a new user profile from scratch (see post above), I realized how much Mozilla has restructured things in the user profile by now.
0 kommentar(er)
