5 ms·

I assume this thing is just a web app rendered in their "browser"? So doesn't it need to do all the things you list? Needs css to layout the DOM, needs to parse

I assume this thing is just a web app rendered in their "browser"? So doesn't it need to do all the things you list? Needs css to layout the DOM, needs to parse and execute javascript. I'm a recent convert from grooveshark, so I've been using the spotlight web player and I find it a pretty nice web app to be honest. I haven't dealt with any of the actual desktop clients yet, so don't know if anything I said above is true.

detaro 11y ago
> I assume this thing is just a web app rendered in their "browser"? So doesn't it need to do all the things you list? Needs css to layout the DOM, needs to parse and execute javascript. From a users perspective, that is an implementation detail and doesn't matter. A users only cares if his music player feels slow or not.
wlesieutre 11y ago
Yes, it appears to be developed on CEF, which could explain the slowness. "We decided to develop it on HTML and JS" is a lame excuse for slow mobile apps, and IMO it's even worse on desktop. Related: http://techcrunch.com/2012/12/13/facebook-android-faster/ http://techcrunch.com/2012/12/13/facebook-android-faster/