3 ms·
"Not to mention the devs will have to rewrite these bits for 64bit support." Huh? Why? "64bit" doesn't change the APIs, at most it should take a recompile to b
by jey 18y ago
"Not to mention the devs will have to rewrite these bits for 64bit support."
Huh? Why? "64bit" doesn't change the APIs, at most it should take a recompile to build against the x86-64 version of the libraries. And thanks to Universal (fat Mach-O) binaries one single executable can contain ppc, x86, and x86-64 versions bundled right into it.
- Zev 18y agoApple isn't going to support 64bit Carbon.
- chrisbroadfoot 18y agoI think the real question is: Why the hell would you need a 64-bit browser?
- Zev 18y agoIf the rest of my OS is going 64bit, why shouldn't my browser? Besides, I would imagine (unfortunately I'm not as well versed in this area as I would like) that there would be a performance gain from using a native 64bit browser on a 64bit OS instead of a 32bit browser on a 64bit OS. True, some plugins for browser (I'm looking at you, Flash) aren't 64bit - yet - but that could be vendors dragging their feet because there's not enough of a demand. Or something else; I'm not privy to what goes on in the upper levels of Adobe. Or any other major company for that matter, but thats not the point of this post.
- pmjordan 18y agoIt gets really messy with plugins, Java, etc. Browser developers have had to jump through all sorts of hoops to get 32-bit plugins (aargh, Flash!) working in 64-bit browsers, (e.g. on x86_64 Linux distros) but it's presumably even harder to do the opposite, use 64-bit plugins from a 32-bit browser. My x86_64 Linux distro has 64-bit Java, for example, which won't work with 32-bit browsers. Aside from that, it won't be long until 64-bit operating systems take over even on the desktop, even in Microsoft-land, and the less 32-bit cruft that is dragged around, the better.