![]() ![]() This is a dedicated 64-bit browser based on Firefox’s open source code, compiled specifically for 64-bit versions of Windows, complete with optimizations to help speed things up a little more. Despite the growing popularity of 64-bit though, we're still in that transitional phase where many applications are still only available in 32-bit builds – they're compatible with 64-bit, but you get none of the performance benefits 64-bit computing can bring.įirefox is one such example: the latest Nightly build is available in 64-bit, but we're at least six months away from it making the transition through Aurora and Beta to a final release.įor those who can’t wait for Firefox to embrace 64-bit, take a look at Waterfox instead. My GPU is a dated Kepler-based Nvidia Quadro, with drivers that Nvidia no longer keeps current.64-bit is the future of computing and one obvious benefit of running a 64-bit version of Windows is the fact it allows you to access more than 3.5GB of RAM, helping speed up your computer. Since Firefox 109 doesn’t have the same issue, it means primarily that they have been able to figure out the right combination of settings for certain thus affected GPUs, just like Google did with Chrome. When it comes to Firefox/Waterfox, I’ve just recently installed Firefox 109, for reference and comparison, and I’m not going to install 102 ESR along with it…īut there is no blur for me in Firefox 109 with ‘performance defaults’ enabled, while in Waterfox 5.1.2, I had to uncheck ‘performance defaults’ and uncheck ‘use hardware acceleration’. Interestingly enough, Microsoft has not gone through the same diligence with Edge, and I had to uncheck their ‘Use hardware acceleration’ option. While I’ve never observed this issue in any stable release of Google Chrome, it was well obvious to me from their detailed GPU-related settings that they have carefully disabled certain parts of GPU-accelerated rendering for certain GPU/drivers. I’m new to Waterfox, but I’ve known this blur for years from… Microsoft Edge!įrom what I’ve known, this has nothing to do with Windows dpi scaling and everything to do with the browser’s accelerated rendering incompatibility with certain GPUs and their drivers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |