![]() dmg is available today, and-as expected-it's significantly faster if you're doing something complicated enough in your browser to notice. That was and still is a true statement we find it difficult to believe anyone using the non-native binary for Chrome under an M1 machine would find it 'slow.' That said, Google's newer, ARM-native. PerformanceIn our earlier testing, we declared that the previous version of Google Chrome-which was available only as an x86_64 binary and needed to be run using Rosetta 2-was perfectly fine. Google has released an updated version of Chrome that’s designed especially for the M1 MacBooks. Presumably, Google is pushing separate downloads due to the much smaller file size necessary for the x86_64-only package-the universal binary contains both x86_64 and ARM applications, and weighs in at 165MiB to the Intel-only package's 96MiB. On any mac (doesnt have to have the M1 chip), use Chrome to go to the 'normal' Chrome download site and select to download the Apple chip version. As you can see, they highlighted the ‘Mac with Intel Chip’ by default. ![]() ![]() Google presents Chrome for download as either an x86_64 package or an M1 native option-which comes across as a little odd, since the M1 native version is actually a universal binary, which works on either M1 or traditional Intel Macs. Google earlier this week released a version of Chrome designed specifically for Apple's M1 Macs, and those with a new MacBook Air, MacBook Pro, or Mac mini will want to download the. So if you’re facing a slow Chrome browsing experience, uninstall your Google Chrome and reinstall the correct M1 version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |