First 64 bits would imply a Cocoa build. Cocoa is Apples way forward.
64 bit apps for the most part are faster. With respect to iTunes speed ups are welcome.
Since loading iTunes forces the Mac OS to load libraries it might not be using running iTunes ises more system resources than is required. This can lead to swappimg and other negative impacts. Using the Cocia libs already in RAMsimply lessens iTunes impact on RAM or it would if it was 64 bit. The savinhs is more than enough to make up for 64 bit bloat.
Going to 64 bit Cocoa would eliminate the possibility of a 32 bit release that ends up being temporary.
Lastly iTumes Status as a consummer app means nothing. You can get music playback with a 16 bit or 24 bit processor if you want. The bitness isn't so much an issue as having an app that optimally leverages an OS as it developes overtime. Since Snow Leopard is very much 64 bit that is what you want your apps supporting.
In a nut shell it is as once a trivial issue but yet important for many users. It is not however a thing worthy of your dismisal.
How does the above apply to all the unix/bsd/legacy-whatever underpinnings of OS X? Much of that code is older than the average iTunes user.
In my opinion, finishing the transition away from legacy quicktime code is what really needs to happen. Carbon-vs-Cocoa is rather trivial compared to that. Remember, "quicktime" includes millions of lines of code that is needed to make iTunes work on Windows...
Well, it?s amazing. The miracle has been done. Hat?s off. Well done, as we know that ?hard work always pays off?, after a long struggle with sincere effort it?s done.
Comments
- First 64 bits would imply a Cocoa build. Cocoa is Apples way forward.
- 64 bit apps for the most part are faster. With respect to iTunes speed ups are welcome.
- Since loading iTunes forces the Mac OS to load libraries it might not be using running iTunes ises more system resources than is required. This can lead to swappimg and other negative impacts. Using the Cocia libs already in RAMsimply lessens iTunes impact on RAM or it would if it was 64 bit. The savinhs is more than enough to make up for 64 bit bloat.
- Going to 64 bit Cocoa would eliminate the possibility of a 32 bit release that ends up being temporary.
- Lastly iTumes Status as a consummer app means nothing. You can get music playback with a 16 bit or 24 bit processor if you want. The bitness isn't so much an issue as having an app that optimally leverages an OS as it developes overtime. Since Snow Leopard is very much 64 bit that is what you want your apps supporting.
In a nut shell it is as once a trivial issue but yet important for many users. It is not however a thing worthy of your dismisal.How does the above apply to all the unix/bsd/legacy-whatever underpinnings of OS X? Much of that code is older than the average iTunes user.
In my opinion, finishing the transition away from legacy quicktime code is what really needs to happen. Carbon-vs-Cocoa is rather trivial compared to that. Remember, "quicktime" includes millions of lines of code that is needed to make iTunes work on Windows...
=====
robet
stretching exercises