A 64bit chip WILL be faster than a 32bit chip... however, it will not be a significant improvement.
Reason #1
Currently, with 32bit systems, a DOUBLE (64bit floating point) and a LONG LONG (64bit integer) requires several clock cycles to make simple calculations instead of one clock to handle 32bit FLOAT and INT. Any application that is using these larger numbers would benefit from the 64bit system. While 64bit integers are not used very often, DOUBLES are the default when it comes to floating point calculations because the 32bit version does not have the resolution that is needed for most calculations. When 64bit systems are the norm, you will see more applications take advantage of the LONG LONG datatype.
Reason #2
The already exists a 64bit version of the FreeBSD Unix OS which is what Darwin is based on. Having an underlying system that is 64bit capable will allow many system operations take advantage of the benefits of 64bits with existing applications.
Reason #1
Currently, with 32bit systems, a DOUBLE (64bit floating point) and a LONG LONG (64bit integer) requires several clock cycles to make simple calculations instead of one clock to handle 32bit FLOAT and INT. Any application that is using these larger numbers would benefit from the 64bit system. While 64bit integers are not used very often, DOUBLES are the default when it comes to floating point calculations because the 32bit version does not have the resolution that is needed for most calculations. When 64bit systems are the norm, you will see more applications take advantage of the LONG LONG datatype.
Reason #2
The already exists a 64bit version of the FreeBSD Unix OS which is what Darwin is based on. Having an underlying system that is 64bit capable will allow many system operations take advantage of the benefits of 64bits with existing applications.