> You're assuming pointers dominate the footprint. No, I just wrote: >> if you have only 8 GB of physical ram, you won't necessarily be able to handle much m

> You're assuming pointers dominate the footprint. No, I just wrote: >> if you have only 8 GB of physical ram, you won't necessarily be able to handle much more than with a 32-bit application That means, I absolutely know applications that won't be better on a 8 GB RAM computer as 64-bit applications, and they were written using standard C++ libraries. Typically, such applications weren't optimized for cases when they use a lot of memory. If somebody competent spends enough time and energy, even such application can be made to use memory better but it's not something that "just happens." And sometimes 32-bits application is a good trade-off. See for example https://blogs.msdn.microsoft.com/ricom/2009/06/10/visual-studio-why-is-there-no-64-bit-version-yet/ https://blogs.msdn.microsoft.com/ricom/2009/06/10/visual-stu... "A 64 bit address space for the process isn’t going to help you with page faults except in maybe indirect ways, and it will definitely hurt you in direct ways because your data is bigger." What I'm trying to suggest is that the topic is more nuanced as "64 doublegood 32."