A Windows developer and Sysadmin has compiled a "Watch List" of the small but annoyingly important things to keep in mind when moving from 32 bit Windows to Windows x64.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
Member since:2005-07-09
I will reply by saying most of my friends have over 4 gb ram. They do video editing, (hd footage), lots of gaming, are java developers etc etc. Whenever I do any sort of development using enterprise oracle products, I can easily use up 2.5 gb of memory. If I was using 32 bit, well that does not leave me with much headroom. And if I am bored, I just stop doing some work and turn on some Crysis without having to turn off any of the software.
My brother who is editing HD footage is already consuming over 4 gb of ram and now he has to go and grab 4 more gb to not cause any sort of disk swapping.
Also as far as I understand, 64 bit processes all have DEP enabled by default. No ifs ands or buts so in terms of security its a good idea.
And also before building machines, we do our research to see what works and does not work. So it just works for us and we are quite happy. 
No offense taken from all the people who asked why. Main thing was memory usage, server based OS and didnt want to upgrade to Vista. Its just a win win situation fellas.
Member since:
2008-09-10
You're right, there are some people who don't need to go 32-bit, and could probably stay that way for several more years.
In my case, and in the case of anyone who's building large-scale apps, the extra memory is a life-saver.
In another case, there are applications (like Microsoft Exchange 2007) that are being released as 64-bit only applications. That's definitely a minor occurrence, but I had to help someone out with that exact situation.