• TwiddleTwaddle@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      9 days ago

      Its a continuation of the now deprecated Clementine music player, which was aiming to bring the Foobar2000 UI and plugin functionality to a modern FOSS cross platform state. That’s off the top of my head, but I followed the Foobar->clementine->strawberry pipeline over the years because I like the Milkdrop2.0 visualizer plugin.

      • h6a@beehaw.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 days ago

        If I remember correctly, Clementine was not trying to bring Foobar to Linux, but trying to preserve the UX/UI of Amarok 1.4 after the release of Amarok 2.0 (which was not well received by the community).

    • upstroke4448@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      10 days ago

      Personally I like it because it makes managing my music library really easy. Especially when it comes to keeping everything organized in a way my Plex server likes as well.

      It really depends on the individual. Some people really hate the outdated looking UI and don’t have much use for the audiophile features.

  • buckykat [none/use name]@hexbear.net
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    10 days ago

    I don’t know what this strawberry music player is, but I approve of the fact that I can install it right from the fedora repos in one click but windows users have to build it from source from an unofficial repo on girhub. All programs should be distributed this way to make windows users suffer.

    • upstroke4448@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      10 days ago

      I don’t think wanting people to suffer is a great goal but to each their own.

      To be fair, building the binary is the same regardless of OS. The creator just decided to send the windows and Mac binaries off to a third party server and then paywall access. You can see this in the build.yml of the original repo.

      • MagnificentSteiner@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 days ago

        The reason macOS and Windows releases are closed to sponsors is because Strawberry has mainly had one contributor/developer over several years. Maintaining releases for macOS and Windows is a lot of additional work, and requires hardware and build environments, building and maintaining all libraries Strawberry depends on, and we also have to pay for a Apple developer account for signed macOS releases.

        From the official website.