Please tell us the advantages using 64bit with 600mb of usable memory. I'm dying to here your response.
64-bit code is, on average,
faster, and, more secure (strong ASLR). Yes, the code is a
little bigger, but, the average code is faster anyway.
Even 64 bit computers after over a decade of being 64 bit are not even taking advantage of it.
I have no idea what you are talking about. Except for MicroSoft apps (e.g. Office) and Google Earth, my Macs are 32-bit free. My iPhone is nearly 32-bit free.
heck not even most high end games are written in 32bit to save space and most are not even multithreaded.
No offense, but, my limited exposure to game quality (a while ago now) is that it is the most sloppily written, fragile pile of throwaway code on the planet. I hope game code quality has improved, but, I wouldn't take games as being exemplars of best practice.
Here is the exact same version of chrome one codded in 32 bit and one arm64 and there is absolutely zero noticeable difference in use and it takes up 2x the space.your advantages are washed out with 1gb of ram when the apps take up 2x the space and fill that ram up.
That looks like the app file has both 32-bit and 64-bit code inside. You are bringing up an interesting Android question. Is it possible to strip the 32-bit code version out when downloading/managing apps? Flash is a scarce resource on phones, and, the environment should strip out unused/unneeded code versions whenever possible.
Back on security: Besides ASLR and DEP, it looks like the development environments should also have a newer security measure, that AFAIK, is still experimental but can be done on FreeBSD on x86-64: CPI-
Code-Pointer Integrity. As far as I am concerned, security is the #1 issue on these classes of products today.