You need to check out how Snow Leopard is built a little better, as it will not be 100% 64bit. It will be 'more' of a hybrid, but still not a full 64bit OS.
Actually, it will be a full 64-bit OS from kernel to user with legacy support for 32-bit carbon and cocoa. By your reasoning, XP 64 and Vista 64-bit aren't 100% either as both use the less-elegant WoW for 32-bit stuff and System32 for the 64-bit bits. This, in addition to the fact that Microsoft requires separate versions, rather than just shipping a product that covers both architectures. There's also that pesky problem that most programs for Windows are 32-bit apps, and many are very fragile on the 64-bit Windows platform. I'll stop now.
Because it DOESN'T matter in the Windows world. 32bit applications get performance benefits on the 64bit OS.
As it also happens with Snow Leopard, as the kernel goes full 64-bit (on Core 2 and newer machines). Current Leopard already gives the 64-bit benefits of increased registers and larger VM space to 64-bit programs, so there isn't a lot more to gain. These capabilities are not magically transferred to 32-bit apps under any OS, as the architecture is different, so there is no way that Vista-64 or Win7-64 will gift 32-bit apps with more than the 2GB of address space that they are currently allowed (vs. the full 4GB that OS X gives to 32-bit apps). Any speed increase comes from taking less time for register shuffles on 64-bit programs, giving more time to all processes.
Also if developers want to provide a full 64bit version, it is a simple recompile, you don't have to re-write the application like a lot of people (Adobe for example) find they have to do on OS X. This is why if you want a 64bit version of Adobe software, you need Vistax64, as the development APIs Apple sold Adobe never got moved to 64bit as promised.
Oh ho! What a canard. A simple re-compile was what has been hamstringing 64-bit graphics drivers and codecs for the last three years or so on XP-64 and Vista-64? Apple doesn't sell it's API's, it just publishes them. Adobe had 8 years of warning and opportunity to move it's cruft from Carbon to a cleaner, more modern API, and they decided to play chicken because Apple started eating their lunch with Final Cut Pro and Aperture. Being Carbon developers, they knew that it would not be an easy to clean up all of the legacy crap in the API without breaking backwards compatibility. Developing the iPhone was the final nail in Carbon's coffin.
All MS API sets(development platforms) move to 64bit, even old 16bit applications can be recompiled as 64bit applications. (You can't do this with System 9 applications, nor even the whole early 32bit transition APIs Apple provided.)
Yes, this is why Microsoft came up with thunking and the 16-bit \System folder and the 32-bit \System32 folder for Win32, which became the 32-bit \WoW and 64-bit \System32 folder. Brilliant. It isn't quite fair to drag System 9 applications into this mess. Do old Borland TurboPascal programs magically compile to 64-bit? Most System 9 programs were done as projects in Metrowerks Code Warrior with the PowerPlant framework, a system that was bought and buried by Motorola. Mac OS 9 was a cooperatively multi-tasked mix of PowerPC and 680x0 code, which used legacy system calls that needed Paschal syntax. OS X is basically a BSD Unix with no 680x0 code that uses GCC for compilation. Different architectures, compilers, system calls, hell the only things that are the same are the word "Mac" and "Apple". Up until the the Intel switch, you could run Mac OS 9 code, similar to WoW, without a re-compile. In most cases, the question is why would you want to.
Do you remember the Apple ads talking about the FIRST 64bit Personal Computer? How ironic that this many years later it still isn't even running a native 64bit OS, where Windows has been doing 64bit versions since the mid 90s. (Yes NT 4.0 versions had 64bit modes and used 48bit addressing space on hardware capable of it, like the DEC Alpha)
Apple is out of their league and making a fool of themselves in the process.
Yes, I remember those extremely expensive DEC Alpha NT PC's. They had what, about three programs available for them? They were great at running bench marks, but didn't even have all of the normal included programs that you got when you bought NT for the PC. I don't remember ever seeing an Alpha running anything other than VMS in the real world. At that time, NT wasn't really good at doing much of anything other than letting you still click things while the hour glass was being displayed. Oh, and what use was one of those Alpha PC's for their 64-bitness if you couldn't install more than 4 GB of RAM or actually run any programs?
At that time, the big push from Microsoft was to entice CAD companies to port their UNIX packages to NT, where the POSIX and OpenGL support was a joke, but still garnered bullet point status on sales literature. I had a newly minted Pentium Pro NT box on my desk with the just-ported Pro/Engineer installed. It was still very-much faster to use the then 8-year old HP/UX box that was also on my desk, to do the work, because it wasn't hanging on network transfers or crashing all the time. NT 4 wasn't really useful until after SP5 was released, and by that time, the non x86 platforms had basically died off. I don't even recall if SP6 was made available for the Alpha.
Apple should have qualified their add to specify that they had the first truly useful 64-bit PC. That would have put them in the clear.
-- Len