4 ms·
Used to work for Spotify back in the days. I was the maintainer of libspotify since its inception (early 2009) and a few years on. TBH I'm surprised it was stil
by andoma 4y ago
Used to work for Spotify back in the days. I was the maintainer of libspotify since its inception (early 2009) and a few years on. TBH I'm surprised it was still being supported up until this day by the backend. Though, some of the earliest hardware integrations were made using libspotify (before the eSDK came about) so I suppose it just had to be kept alive longer than otherwise would have been needed.
RIP <3
- mschulze 4y agoHey, Cool to see someone who worked on this :) Back in the day I wrote a (probably really bad, not a C/C++ developer) wrapper around libspotify for Node.js: https://github.com/FrontierPsychiatrist/node-spotify https://github.com/FrontierPsychiatrist/node-spotify At some point it could do enough for me to build a webapp with Node.js running on a Rapsberry Pi to stream Spotify. I even got contacted by Spotify to take down the domain node-spotify.com for it.
- juanci_to 4y agoHow was it working for Spotify? They are kind of an interesting company for me
- tommiegannert 4y agoI agree. Seems it had a good run. I still remember the fairly long discussions of whether to make the public API C or C++. Fun times. :)
- gaws 4y ago> C or C++ How did Spotify land on C?
- tommiegannert 4y agoThe client itself was C++, so it would have been the natural choice. But we didn't want the ABI liability since it was shipped in binary form. So libspotify became a thin C-wrapper over the C++ core. That way, we didn't have to worry about vtable layouts blowing up.