The Google I/O logo is seen on the stage prior to the keynote speech at the Google I/O developers conference in San Francisco
The Google I/O logo is seen on the stage prior to the keynote speech at the Google I/O developers conference in San Francisco June 25, 2014. Reuters/Elijah Nouvelage

Last June, Google introduced the 64-bit Chrome. However, it was only available in the browser's Canary and Dev channels. Come July, the beta channel went through the same thing. This time, the system is now available via a stable channel.

According to Google, the 64-bit system offered graphics and speed improvements along with media benchmarks. As noted in the Chromium blog: "For example, the VP9 codec that's used in High Definition YouTube videos shows a 15% improvement in decoding performance. Stability measurements from people opted into our Canary, Dev and Beta 64-bit channels confirm that 64-bit rendering engines are almost twice as stable as 32-bit engines when handling typical web content."

There are also improvements in security according to the post. Specifically, the blog states: "Finally, on 64-bit, our defense in depth security mitigations such as Partition Alloc are able to far more effectively defend against vulnerabilities that rely on controlling the memory layout of objects."

According to Tech Crunch, users can also expect better memory usage and speed from the 64-bit Google Chrome for Mac. The 64-bit beta build for Mac came after Google announced the 64-bit Chrome for Windows as "stable." Similar to other Chrome releases, the 64-bit support can only be accessed through the Beta channel initially. People will not find it within the Chrome standard build accessible to most users. The consolation is that people can obtain it in a form that will not possibly break constantly. Most users will not see the difference between the speed of the previous Chrome and current beta. The big advantage is on how the system will run overall. People can expect a smoother transition or functionality from the system.

Majority of OSX apps, the popular ones, are already running on or based on the 64-bit system. This means that when 32-bit platforms like Chrome are used, the system needs to work with additional memory and to run them. If the system is based on a similar structure then the easier to load and run operations. Given the user will not be working with other 32-bit programs then this can free up more memory for other purposes. It's a win-win deal.