Live data from Hacker News

Chrome for Mac 64-bit Support

code.google.com

71–80 of 84 posts

Re: Chrome for Mac 64-bit Support

#71

So wait - I downloaded the 64 bit 39.0.2171.65 version. Because of this, I finally updated my Java version (now 8.25). I still can't java applets to run in Chrome. What gives? I still get Verify Java Version32-bit Chrome does not support Java 7 and later versions on Mac OS X. Java runs only on 64-bit browsers. http://javatester.org/version.html Gives an error - Java needs your permission to run, but I've already allo…

Try going to System Settings and then the Java control panel. Locate the Java applet runtime configuration and make sure it's pointing to Java 8 and not some random Java 7 applet runtime the upgrade left behind. Java has system wide preferences for runtimes of both the full JRE and the plugin, separately.

Failing that, go to java.com and see what their check says.

Re: Chrome for Mac 64-bit Support

#74
post #28

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

It ought to work with Handoff and let you open iOS Safari's current web page in Chrome. Currently you get a popup with the Chrome icon but it doesn't work because Chrome isn't 32-bit(!)

Re: Chrome for Mac 64-bit Support

#76
post #2

Oh, wow, didn't know that Chrome was still 32-bit on Macs. The Linux builds have been 64-bit since early 2009, and Windows went 64-bit earlier this year. Congrats to the Chrome team. :) (FWIW, Firefox has been 64-bit on OS X and Linux since 4.0, but we're still working on Win64 support. Of course, Microsoft kicked everyone's ass when they released Windows XP Professional x64 Edition in 2005, which included a 64-bit v…

From what I have read, for software which wasn't originally developed for Windows, especially if the code base is old enough, porting to 64-bit is harder on Windows than on other systems.

The problem is that, while the Unix-based world went the LP64 way (int is 32-bit, long and pointers are 64-bit), Windows went the LLP64 way (int and long are 32-bit, pointers are 64-bit). A lot of Unix programmers tended to behave as if "long" was the largest native type ("long long" on 32-bit uses a pair of registers). They have to scrub their whole code base for things like assuming an object's size or array index will always fit on a "long".

For software originally developed for Windows, LLP64 was supposed to make porting easier, since unlike on the Unix world (where "long" could be 32-bit or 64-bit), a lot of Windows programs assumed a LONG was always 32-bit, and that assumption was baked into file formats and IPC protocols.

Newly developed software has it easier; programmers nowadays keep in mind that there are relevant systems where sizeof(long) ----

As for Mac OS X, the porting problem is Carbon. If the code base is old enough, it'll be using Carbon, which AFAIK is not available for 64-bit.

Re: Chrome for Mac 64-bit Support

#77
post #13

Earlier quoted context omitted.

I just checked chrome://chrome for updates and it confirmed there was no update and 38 was the latest, but when I re-downloaded chrome from https://www.google.com/chrome/browser/ it was the 64-bit v39 - so yes you do need to install a new version!

But that doesn't make sense - if it's true that they will not be providing a 32bit version for Mac from now on. Then most people will be stuck on version 38.

[deleted]

Re: Chrome for Mac 64-bit Support

#78
post #74
post #28

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

It ought to work with Handoff and let you open iOS Safari's current web page in Chrome. Currently you get a popup with the Chrome icon but it doesn't work because Chrome isn't 32-bit(!)

I thought that Handoff was broken. Still broken in the sense that no error message is shown for an invalid exchange.

Re: Chrome for Mac 64-bit Support

#80
post #2

Oh, wow, didn't know that Chrome was still 32-bit on Macs. The Linux builds have been 64-bit since early 2009, and Windows went 64-bit earlier this year. Congrats to the Chrome team. :) (FWIW, Firefox has been 64-bit on OS X and Linux since 4.0, but we're still working on Win64 support. Of course, Microsoft kicked everyone's ass when they released Windows XP Professional x64 Edition in 2005, which included a 64-bit v…

Congrats to the team for doing something many many years late?
Post reply on HN