Linked by Kroc Camen on Thu 4th Dec 2008 18:20 UTC
Permalink for comment 339222
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2005-09-21
"The Mac download expands into a 117 MB"
I pretty much lost interest after that. For me, a music player should be something to play music in the background and use minimal resources doing so. I don't need some behemoth running in the background all the time, integrating every single online source of information into the app itself on the off-chance that I might want to look that stuff up.
By all means, allow me to get to the wikipedia/lyrics/pictures page for an artist/song, but why people think embedding this info into a music player is a good idea is beyond me. Those things exist on the web, and the correct tool for viewing them is a web browser. Instead of embedding a browser engine in your app, launch the browser with the correct link so I can view it properly and maintain the separation of responsibilities between apps.