• BeigeAgenda@lemmy.ca
    link
    fedilink
    arrow-up
    17
    arrow-down
    2
    ·
    4 months ago

    Because it’s easier to use the version that’s in the distro, and why do I need an extra set of libraries filling up my disk.

    I see flatpack as a last resort, where I trade disk space for convenience, because you end up with a whole OS worth of flatpack dependencies (10+ GB) on your disk after a few upgrade cycles.

    • F04118F@feddit.nl
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      4 months ago

      Is compiling it yourself with the time and effort that it costs worth more than a few GB of disk space?

      Then your disk is very expensive and your labor very cheap.

      • cley_faye@lemmy.world
        link
        fedilink
        arrow-up
        12
        arrow-down
        1
        ·
        4 months ago

        For a lot of project “compiling yourself”, while obviously more involved than running some magic install command, is really not that tedious. Good projects have decent documentation in that regard and usually streamline everything down to a few things to configure and be done with it.

        What’s aggravating is projects that explicitly go out of their way to make building them difficult, removing existing documentation and helper tools and replacing them with “use whatever we decided to use”. I hate these.

      • BeigeAgenda@lemmy.ca
        link
        fedilink
        arrow-up
        8
        ·
        4 months ago

        I should have noted that I’ll compile myself when we are talking about something that should run as a service on a server.

      • recarsion@discuss.tchncs.de
        link
        fedilink
        arrow-up
        3
        ·
        4 months ago

        99% of the time it’s just “make && sudo make install” or something like that. Anything bigger or more complicated typically has a native package anyway.

      • ReveredOxygen@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        4
        ·
        edit-2
        4 months ago

        They didn’t say anything about compiling it themselves, just that they prefer native packages to flatpak

        edit: I can’t read

        • Batbro@sh.itjust.works
          link
          fedilink
          arrow-up
          9
          ·
          4 months ago

          2 comments up they said

          If the choice then is flatpack vs compile your own, I think I’ll generally compile it, but it depends on the circumstances.

    • TimeSquirrel@kbin.melroy.org
      link
      fedilink
      arrow-up
      8
      arrow-down
      6
      ·
      edit-2
      4 months ago

      I mean it’s 2024. I regularly download archives that are several tens or even over 100 GB and then completely forget they’re sitting on my drive, because I don’t notice it when the drive is 4TB. Last time I cared about 10GB here and there was in the late-2000s.

      • BeigeAgenda@lemmy.ca
        link
        fedilink
        arrow-up
        3
        ·
        4 months ago

        Yep that’s all well and good, but what flatpack doesn’t do automatically is clean up unused libs/dependencies, over time you end up with several versions of the same libs. When the apps are upgraded they get the latest version of their dependency and leave the old behind.

      • azenyr@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        4 months ago

        I don’t know what dependencies he has but my 3 year old system that is constantly being updated is full of flatpaks and all of the dependencies combined are only around 3GB. People see 1GB of dependencies and lose their mind.