The poster asked that people follow up in a different newsgroup.
Beyond that, there's all the infrastructure you need to stand up for development, continuous integration, QA, metrics, and shipping to hundreds of millions of users. The logistics of that part are almost the same as supporting an entirely new OS, and in the case of Windows it's one with an insanely large and diverse population. So yeah, that parts actually a lot worse just because of the sheer numbers.
So the need in Chrome to go 64- from 32-bit from a memory perspective is less.
The only plugin i have is the JRE - which has provided a 64-bit version for over 10 years (SPARC64 in Java 1.4). And i can't remember the last time i chanced upon a Java applet in a webpage.
Even the Unity3D Web Player has a 64-bit browser plugin. I can't imagine what's really missing other than outdated versions of RealPlayer.
Yep. I'd prefer in Firefox (and others) abandoned 32-bit windows instead.
Windows Server 2012 does not have a 32-bit version, it's 64 bit only.
Related, why is there a 32 bit build of Windows 8? Does some of the target hardware at the low end of the market need it? I guess the server space has has a higher threshold of minimum hardware than tablets.
I figure that, sometime in the next 10 years, 32-bit OS'es will go the way of 16-bit OS'es. The time to iron out the bugs in the 64-bit version is now, while it's only used by diehard techies who understand the necessity of switching to 64-bit.
If we wait until the unwashed masses are forced to switch by ever-advancing technology, they'll jump ship for browsers that have been preparing for years.
Also, the fact that the link has exactly one post in between the proposal and the switch tells me that nobody noticed it, and more effort should have been made to get community review, buy-in, sign-offs. There should have been lots of commentary and input on such a fundamental feature as 64-bit support in such a high-profile open-source project.