![]() ![]() ![]() If you’re on a Mac I recommend rolling with the Canary channel. Chromium developers have built a ‘fail safe’ into the server infrastructure that distributes updates to ensure that only compatible builds can install on compatible systems. On a 32-bit system? There’s no need to panic. Data on Mac performance has yet to filter out but it’s a promising indication nonetheless. Windows 64 bit Chrome builds have boosted performance by 25%, say Google, while also improving stability. ![]() 64-bit builds allow Chrome to ‘address’ (read: use) more available memory on your system (assuming you have it) and perform more tasks concurrently, and faster. What are the benefits of the switch? On paper: better performance and better multitasking. As of Chrome version .0 on OS X, 64-bit Chrome is a-go on the dev channel: Latest Developer Channel Release Benefits Now it seems as though that testing is ready to go wider. In fact, if you use the Canary channel frequently you may have already used one, as developers often seeded builds for testing there on occasion. Most recent versions of Apple’s desktop operating system no longer default to the 32 bit architecture, a move that has seen some third-party plugins for the platform, like Java 7, offered only in 64-bit versions.Ĭhromium developers have been working on bringing native 64 bit builds of Chrome to OS X for a while. ‘Google quietly updated Chrome to a 64 bit build without you noticing!’ ![]()
0 Comments
Leave a Reply. |