Hacker News new | past | comments | ask | show | jobs | submit login

> It's using 160mb of ram

And that is acceptable for a music player ???.




Maximised on my 4k display I see 26 album arts which look high resolution. How much ram would that take decoded?

There's also the song data for what's playing now and next song.

You don't seem to understand what the application is doing.


Just show and play my music and not drag along the entire Chrome web browser to do that.


The chrome rendering engine plus node js.

Why is that so different from Java or .NET?

Simply because it's an easy meme.


A standard length flac is easily 30mb and presumably the player keeps the current and potentially next in memory. Add in a few high res icons for album art and you can get 100mb before the UI... exists. It's great that Winamp could play your 128k mp3s and show your text only list in the 00s, but it's not like expectations haven't gone up in a way that contributes to memory use




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: