Is Chrome For Mac 64 Bit

I wonder if Chrom's 32 bit architecture is connected with the battery performance issues that people are having? See, e.g.: Chrome is one of the least efficient programs that I run on OS X. Safari consistently uses fewer resources, even when I leave the same tabs open in both Apps, yet the Safari add-ons for Evernote, google talk, and google translate are not nearly as reliable as what is available in Chrome. I wish that we didn't have to make such tradeoffs with browsers. Ironically, some of the biggest resource hogs within chrome are the ones built by Google. For instance, Google Hangouts is the worst. I can process raw images all day without generating enough heat for my fan to spin up, but it spins up within seconds of launching a Google hangout.

One day, we're going to start rating how much battery different apps burn through and judging them accordingly. Chrome will not fare well. Rbt_stack 28/1/2014, 16:02 น. To be fair to the Chrome developers, Chrome browser uses more resources per tab because it's sandboxed. It's like trying to run Windows from within the Mac operating system. Each tab needs code and sandbox access that other browsers wouldn't care about. That's because Chrome cares very much about security.

If you're sandboxed then even poorly designed code is protected from hacking. You can see that Chrome has far fewer security advisories as a result of this.

Anyways, that's why Chrome takes more memory and resources. Also, each Chrome tab is a separate process for both security and more importantly a Chrome tab can crash (normally caused by a plugin) and not take down every other tab. My understanding is they can use the same code they just need to port it over to 64bit. To do that they only need to change the ints and longs and points not all data types. There are disadvantages to change all data types. In Many cases a programmer does not even have to go to that length.

He or she only needs to recompile the code with a compiler that supports outputting in 64bit. The actual coding, if that's hole they go about this, takes about 6 months at most because they are changing.

Aug 28, 2014 - Just about every Mac you'd see in operation nowadays has a 64-bit CPU tucked inside. Apple started making the switch from 32-bit to 64-bit.

Porting over, not building from the ground out. The compiling, that only takes about two hours at most.

So I do not buy the claims that they are working on this. To me it seems like they just do not even care.

Iavswn 15/2/2014, 1:24 น. Edit: My understanding is they can use the same code they just need to port it over to 64bit. To do that they only need to change the ints and longs. There are significant performance disadvantages to changing all data types, so they do not need to do that. Only the pointers need to be coded for 64bit.In Many cases a programmer does not even have to go to that length. He or she can just recompile the code with a compiler that supports outputting in 64bit.