64-bit Mac app, would use less memory

Question

Spotify is the last 32-bit app on my Mac.
That means when it's launched (which is all the time), OS X has to load all the system frameworks into memory a second time, but now the 32-bit versions of them, next to the 64-bit versions already there. Just to accommodate Spotify. (source: https://developer.apple.com/library/mac/documentation/Darwin/Conceptual/64bitPorting/indications/indications.html)
As such, Spotify invisibly takes up way more memory than what it actually needs to run. 
I can understand the need for Spotify to be backwards compatible with 5+ years old Mac hardware in use as media players and such, but that can be accommodated with a fat binary, including both 32-bit and 64-bit code.
In 2013, it is a bit strange that lots of Mac users of Spotify have to pay this memory burden of the past, while where is an elegant solution available in the form of fat binaries.
Another thread about this subject:
http://community.spotify.com/t5/Help-Desktop-Linux-Mac-and/No-64-bit-Mac-version/m-p/85001

Answer 1

Hi, OP here.
Focusing on the quality of the desktop app after improving the looks is a good idea, but it is a very strange argument for marking this idea as "Not Right Now", because this idea is all about the fundamental quality of the Mac desktop app.
I guess the staff monitoring here aren't really the technical folks responsible for these decisions, or they are more knowledgeable about the Windows or Linux platforms as opposed to OS X, but let me point out the relevant bits from the documentation I linked to earlier:
Similarly, in v10.6 and later, the first non-64-bit-capable application pays a performance and memory footprint penalty because OS X must bring in the entire 32-bit framework stack. Thus, if you are primarily targeting OS X v10.6 and later, you should be 64-bit if at all possible.
A 64-bit app can consume significantly more memory than a 32-bit app. For this reason, it is tempting to continue to ship 32-bit apps. However, this is usually not the right thing to do.
In OS X v10.6 and later, most built-in apps are 64-bit. The first time you run a 32-bit application, all of the 32-bit framework slices must be loaded into memory. This means that loading older, 32-bit-only applications causes significant memory pressure, particularly on computers with limited RAM. This often outweighs the additional memory impact caused by larger data structures.
This has been the case since 10.6 was released well over 5 years ago.
Now, the probable reason Spotify has been delaying this is their use of the Chromium Embedded Framework, which has been 32-bit only for a  long time. In August 2013 however they introduced 64-bit builds for Windows and Mac OS X with version 3.1547.1412.
So it seems there shouldn't be any bariers anymore for Spotify to release a 64-bit capable update for the Mac client. Please do so!
Google says this about the benefits of using 64-bits Chromium, which would also apply to Spotify:
64-bit Chrome has become faster as a result of having access to a superior instruction set, more registers, and a more efficient function calling convention. Improved opportunities for ASLR enhance this version’s security. Another major benefit of this change comes from the fact that most programs on a modern Mac are already 64-bit apps. In cases where Chrome was the last remaining 32-bit app, there were launch-time and memory-footprint penalties as 32-bit copies of all of the system libraries needed to be loaded to support Chrome. Now that Chrome’s a 64-bit app too, we expect you’ll find that it launches more quickly and that overall system memory use decreases.
Now, for everyones enjoyment and inspiration, a pretty picture of a rather large cat: