Grooveshark and Flash memory consumption
Posted by Tariq • Sunday, March 14. 2010 • Category: Rants
I am not sure what to say in this post without saying too much. Let me start with WTF is the point of flash? If you know a good reason please tell me because I can't think of a single reason why I would ever use Flash over another solution. Let's take the example that instigated this post. Grooveshark, a somewhat nice service. Do a search, get an inferior quality track, play it, save it on a play list for when you want to listen to inferior quality music later. Great. Now surely searching for music and playing it can't be that difficult, right? If true then why the frack, pardon my Caprican, does it use 142MB of memory and lock up my processor to accomplish this task?
I'll stop now. Grrr. Sorry, there's more. Sometimes you hear things like "crappy flash = crappy flash developer" in which case there must be some sort of satanic level conspiracy going on. If ... *deep breath * ... OAO.
I'll stop now. Grrr. Sorry, there's more. Sometimes you hear things like "crappy flash = crappy flash developer" in which case there must be some sort of satanic level conspiracy going on. If ... *deep breath * ... OAO.
3 Comments
The memory usage isn't an issue - certainly nowhere near as hungry as Grooveshark.
On that note, the future of streaming is using HTML5 (not Flash, or even a downloadable app) but that's a blog post in itself...
Good question. The reason it should run in the browser is because if you upload your music to the cloud, you can access it anywhere, on any internet connected device. It's also great as backup - if your hard drive goes down, then you have a copy stored safely. A browser is just the best way of ubiquitous access.
Also, by utilising the cloud, the cloud can be used what it is is great for - discovery and social using tracks from millions of users.
Add Comment