Why the hell most Microsoft programs are still 32-bit by default? Even FSX Steam Edition is installed by Steam using the 32-bit flavour without asking me about it. Is it for compatibility reasons? |
Why the hell most Microsoft programs are still 32-bit by default? Even FSX Steam Edition is installed by Steam using the 32-bit flavour without asking me about it. Is it for compatibility reasons? |
It makes sense.
> [...] most of the time, staying with 32-bit and reducing the amount of memory being consumed will have a much larger impact for both the application and the operating systems as a whole.
This isn't VHS vs Bluray; it's much harder to explain why there is an advantage when it can't be seen. The 64 not version isn't 35% faster, or has dozens of new features. It's mainly just compiled differently, and it is hard to explain memory limits and instruction sets to people.
But, does a program can use more than 4GB of RAM if it's compiled in 32-bit and executed into a 64-bit environnement (with more than 4GB of memory)?
I imagine that the answer is between yes and no.
I imagine that you, as developer, can choose between limiting your program not to use more than 4GB or let the system (host) do the memory re-mapping job for you...
But what about reliability in this case?