• yetAnotherUser
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    3 months ago

    Fully agree, but the way it’s worded makes it seem like log being a text file is the issue. Maybe I’m just misinterpreting intent though.

    • meeshen@vegantheoryclub.org
      link
      fedilink
      arrow-up
      29
      ·
      3 months ago

      200GB of a text log file IS weird. It’s one thing if you had a core dump or other huge info dump, which, granted, shouldn’t be generated on their own, but at least they have a reason for being big. 200GB of plain text logs is just silly

      • xantoxis@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        ·
        3 months ago

        no, 200gb of plain text logs is clearly a bug. I run a homelab with 20+ apps in it and all the logs together wouldn’t add up to that for years, even without log rotation. I don’t understand the poster’s decision to blame this on “western game devs” when it’s just a bug by whoever created the engine.

        • MoonMelon@lemmy.ml
          link
          fedilink
          English
          arrow-up
          5
          ·
          3 months ago

          Agreed, and there’s a good chance that log is full of one thing spamming over and over, and the devs would love to know what it is.

      • pancakes@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        It could be a matter of storing non-text information in an uncompressed text format. Kind of like how all files are base 0s and 1s in assembly, other files could be “logged” as massive text versions instead of their original compressed file type.