Tell what 64-bit brings other than +4GB RAM and i'll tell you that you can add that to a 32-bit CPU too. There is only two things that aren't, more RAM and manipulation of 64-bit integers. The amount of times you to need to manipulate a number as 64-bits integer is quite low.
Bit rash to discount the possibilities that 64 bit brings to flexibility, accuracy, etc of storage and manipulation of data types. end users will not see this, correct. Devs do. .
this was the big draw to 64 bit at release. this was the playground of Sun sparc and other vendor specific unix distro's (HP unix systems) way back in the day as an example. They were 64 bit long before 64 bit was even a household name.
You didn't have the 64 bit for 128gb machines of uber ram...cost prohibitive back in say late 90's. it was 64 bit machines with ram levels equal to 32 bit of the day. Its just you had more freedom working the data aspects.
Plus the usual stance of your developer has to code an application well to get the most from it. Some don't do this. bad or inefficient code...better specs only increase performance so much. You can only muscle (crap) code so much. It is quite possible to make one's code run much better by going back and reworking code. Some don't do this.
Code works (mostly), people want this new whiz bang UI feature....make that happen. Why I hate agile programming so much. We must have new new new to meet demand. How about fixing you older broke ass code. Nah...its easier to slap on new stuff, make most people happy. I mean everyone likes spaghetti, right? Well like spaghetti code too.
This is where some of you are seeing your memory need.
1. Inefficient code not retouched so leaks and other inefficiencies not addressed well (if at all).
2. Throw in new shiny make the people happy UI feature (needs more ram)
1+2= your ram use going to crap.
Rewrite the code to fix 1....and better resource usage makes putting in the new UI not as bad not changing ram amounts. If only they did that. Some do. And I thank them. Wished more would.