According to this: https://forums.overclockers.com.au/threads/winamp-memory-usa...

Winamp 2.72 only used about 8 megs of RAM.

Eight Megs And Counting.

Wow, eight megs was once so much memory that we would laugh about applications that even approached it.

It's really crazy how quickly things have gotten bigger. I remember not too long ago my mid-high power computer had 1Gb of RAM, nowadays that would be laughably small.

Hi, I'm glad you like it! The performance is not _that_ good at the moment, mostly because of superfluous paints, but it's something I'd like to focus on (as it's one of the primary objectives).

So Electron is the problem. It gets worse if you have lots of tabs open in Chrome + running other electron apps as well. A visible and obvious improvement when compared with a native app.

Also, Electron apps do not scale and it wastes CPU time, eats RAM up and fills up HDD space. On laptops, it drains the battery faster.

A quadruple negative to the user.

The second one should be sorted by name to show that there are actually multiple spotify processes. (There's another one near the bottom of the list.)

I wonder what the footprint will look like once the author writes in all of the missing features

I wonder if that executable is stripped, often that saves a decent chunk of memory.

It'll save disk space but not resident memory? Debug symbols etc shouldn't be paged in. The Linux binary goes from 20MB to 10MB stripped.