Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chrome for Mac 64-bit Support

code.google.com

Post reply on HN
Print view View original

61–70 of 84 posts

Re: Chrome for Mac 64-bit Support

#61

Post by eridius »

rtpg wrote: post #33
limsup wrote: post #8

Can someone explain why this wasn't done long ago? What are the difficulties of putting out a 64 bit build?

I know for a long time there was an issue with Flash not supporting 64 bit browsers (and a browser without flash was hard to sell)

That can't possibly be the issue. Plugins like Flash run in a separate process, which can remain 32-bit if required to do so by the plugin while the browser itself goes 64-bit.

Re: Chrome for Mac 64-bit Support

#63

Post by jurip »

coldtea wrote: post #56
Terretta wrote: post #55

Earlier quoted context omitted.

The "well, now that the last 32 bit app on your Mac gets with the times, life's gonna be better" comment shows (a) this wasn't just about Java, and (b) they knew they're way behind the times.

For one, it's far from the "ast 32 bit app" on the Mac. Second, even some Apple apps took some years to be released as 64 bit after the transition. Third, it's not like 64 bit apps get some magic cookies and unicorn love. Millions of Mac users used 32bit Chrome just fine and didn't even know about it (being 32bit).

At the moment, the only thing keeping 32 bit frameworks resident on my Mac is Dropbox. I'm sure there's plenty of legacy apps out there, but it looks to me like it's not that common anymore.

Re: Chrome for Mac 64-bit Support

#64

Post by r00fus »

Raptor22 wrote: post #32
millerm wrote: post #25

Earlier quoted context omitted.

Yes.

What about if you had pages open that you don't want to lose (literally hundreds of tabs)?

Why not save open tabs as bookmark folder? Then reopen the bookmark folder as a tab-set? I know you can do this with FF (maybe +ext).

Re: Chrome for Mac 64-bit Support

#65

Post by riffraff »

dmishe wrote: post #42
dchuk wrote: post #28

Can anyone here explain the benefits of upgrading to this versus using v38 (32 bit)? Battery life? Less RAM usage? Faster?

With current ram sizes this might be negligible, but 32bit chrome would have to load 32bit versions of all system frameworks, while you have 64bit in memory all the time. The less 32bit apps you have, the better :)

I imagine this might affect startup times too? I.e. you are likely to have the 64bit frameworks already in memory while you have to load 32bit from disk when starting chrome.

(Chrome startup is so slow on my machine that this might be negligible anyway).

Re: Chrome for Mac 64-bit Support

#66

Post by rlanday »

Animats wrote: post #62

There's something terrifying about a web browser needing more than four gigabytes of memory.

x86-64 programs run faster regardless of how much memory they use because they get access to more registers. There’s also the issue that loading a 32-bit application when everything else running is 64-bit requires loading 32-bit versions of all the libraries it uses, so ideally at some distang point in the future, all applications will be 64-bit.

Re: Chrome for Mac 64-bit Support

#70

Post by mikeyouse »

empressplay wrote: post #68
mikeyouse wrote: post #67

Just checking.. does the page https://dev.twitter.com/ load for those who've upgraded to the 64-bit OSX Chrome? Reliably crashes for me now..

seems to work fine for me. 10.6

Thanks.. figured it was something local but I appreciate the sanity check.
Post reply on HN