... aaaaaand once again we have armies of people that know nothing about what it really means to have 64bit architecture thinking they know what it means (it's really only for >4GB RAM!) trying to agree with other people that also don't fully understand all the implications.
There are a few of us that write software, and have for many, many years, that deal with 32bit vs 64bit hardware at a deep enough level that can't do much more than cradle our heads in our hands when this sort of dialogue barfs forth on the forums, blogs, or idiotic declarations like this tool from Qualcomm (who, really, should know better but is taking advantage of the public's understandable lack of true knowledge in this area).
There are many types of applications that will see an improvement running on a 64bit platform as opposed to 32bit. There are many that won't. All of us run a mix of those apps that will and will not benefit from having a 64bit CPU and a 64bit bus underneath them. Some of the apps that benefit will see minor improvements, some will see huge improvements. Blanket declarations like '>4GB of RAM is the only real reason to use 64bit' are borne out of the birth of 64bit penetration in the consumer PC market where sales people at Best Buy and Fry's pointed out, when asked by potential customers "why should I get a 64 bit system", responded with the RAM answer. It's a correct answer. It's just nowhere near a complete answer.. it's simply the easiest one to explain and the easiest one for a layman to understand. That's grown into this fallacious concept that the only real reason need it is for RAM access beyond the 4GB mark.