muxamp

I'm really excited about this kind of service. People have been moving increasingly online in everything they do, and music is no exception. I believe that in the future the vast majority of media consumption will use streaming. (As if it isn't, already!) My main side project involves this kind of service, so I know at the very least it can be complicated to write a server/website which can chomp diverse APIs. [1] What puzzles me is how this could be monetized--I'm sure YouTube and SoundCloud aren't in a hurry to stream their media for free without seeing license fees. [1] https://github.com/fruchtose/muxamp

In other words, promises allow us to separate concerns. Document retrieval is one concern, collation another. Other programming languages have this too. They're called a 'METHOD'. Sorry, couldn't resist. On a serious note, look at your code in here: https://github.com/fruchtose/muxamp/blob/master/lib/playlist... And look at your 'playlistCount' function on line 39 (which for no apparent reason you've made a variable). Now I can't understand how a promise there is helping your programming. In fact it seems to have vastly increased the complexity of the code and it is now completely unclear from a quick scan how the method works, what the program flow actually is. It should be a much shorter function, literally just this: function playlistCount(){ return db.query('SELECT COUNT(id) AS count FROM Playlists;', function(rows) {

I can speak your comment, since my side project is a Node.js server that talks to several APIs, a database, and N web clients. Like you, I've worked more than a year on it, but I had a positive experience with Q [1] and jQuery promises. Promises make async code easy to manage, even at scale. Each API request gets its own promise. What happens inside that promise doesn't matter, as long as it returns a result or an error. If talking to the API takes one request or two, it does not matter with promises. We can abstract these API requests in such a way that even if document retrieval is a multi-step process or a one-step process for each document source, the collation process can know nothing about the retrieval process to work. In other words, promises allow us to separate concerns. Document retrieval is one concern, collation another. Prom

Hey HN! I've been working on Muxamp for over a year now, and I decided that there's no point in keeping the source closed. (I never planned on making money from it.) I've learned a lot since I started, and I hope others can benefit from its release--and perhaps teach me a thing or two as well :)