[–] 2 points 4 months ago (2 children)

I did cut back significantly since that initial switch. At one point, I had 1TB of music. Right now it's sitting at ~210MB of mp3s. Quod Libet uses less RAM than Firefox, Thunderbird, or RSSHub, but it is sitting at 4th place on my system.

I don't think there's a way to scale music libraries to these obscene sizes without impacting RAM. Unless you manage it strictly with a file manager and open album folders individually with a lightweight player used only for playback.

  • source
  • parent
  • context
  • [–] 2 points 4 months ago

    And the queries work with custom tags, which can also be added to any element of the UI. It's so good if you're ADHD about organization.

    I love how I can type things like #(added < 1 week) to search for albums I recently added to my library.

  • source
  • parent
  • context
  • [–] 1 point 4 months ago (4 children)

    What a strange take. When I first switched to Linux in ~2009 I tried a ton of other players. Weirdly, Quod Libet was the only performant option back then. Amarok, Rhythmbox, Banshee, Clementine, etc all chugged to load my library with their UIs freezing for upwards of half an hour before I had something usable. Quod Libet just worked.

    Right now it's using 598MB with a music library of ~31K songs.

  • source
  • parent
  • context
  • [–] 6 points 6 months ago*

    This is the biggest issue with CSDs aside from the wasted space coming from oversized buttons. Every developer's gonna put different, inconsistent things in that title bar.

    The close window button is basically universal, but what if I want to minimize the application? What if I want to pin it to all workspaces, stack it on top of other windows, or roll it up? With CSDs there are no standards.

  • source
  • parent
  • context
  • view more: ‹ prev next ›