this post was submitted on 05 Nov 2025
61 points (95.5% liked)
Linux
10016 readers
473 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You think a dedicated app is going to use less RAM than a browser window?
RAM is only expensive if you're dumb enough to buy a modern Mac.
Uh... yes?
Spotify memory usage: 450MB
Rhythmbox memory usage: 95MB
A browser is one of the most complicated applications commonly running on a computer; its code is massive before you load in the mountains of javascript. Also that is measured by RSS - the difference is even starker when you bear in mind that of the 50MB that rhythmbox might be sharing with other processes, most of it probably is being, because a lot will be graphical toolkits used by other programs. Spotify has a smaller fraction, at about 130MB, and god knows what it's pulling in and is able to share with e.g. the main browser process.
RAM is only not expensive in desktops. In laptops, getting more RAM almost always means getting a higher-tier laptop in other ways which adds a lot to the price.
Spotify is not a browser, it's an app.
That's only true if you buy soldered RAM. Don't do that.
It for a fact uses CEF: https://www.spotify.com/us/opensource/
Chromium Embedded Framework literally describes itself as follows on its Git repos: "Chromium Embedded Framework (CEF). A simple framework for embedding Chromium-based browsers in other applications."
The Spotify "app" is mostly just web app code running on top of a single page Chromium instance, meaning for the most part, it isn't truly native.
And takes more resources than a tab because it doesn't share them, it has its own copy.