If I had a wish for christmas from GabeN or Valve in general, it would be actually meaningful error messages from steam.

If I had two wishes, I would like a community tool to share configs to make games work that require tweaking.

But I’d be very happy if I got better error messages.

  • thingsiplay@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 hours ago

    No one argued it would be a trivial issue. But how do you know its not a trivial issue? To me this does not look like a hard thing to implement, its more a design choice and a design failure. If they have the data to write into log, they could have given SOMETHING more useful (like the filename in question) with the error message.

    • ReptilianCleric@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      10 hours ago

      Well, for starters, your application is confirmed to not be operating correctly; essentially, you cannot necessarily count on anything behaving correctly. Another issue is parsing the log - while it’s not too difficult to check if it’s a disk related issue, accurately and successfully parsing the specific cause is maybe not so easy. It really depends, and depending on what the software does there are all sorts of odd little seeming issues that can make the whole process a headache.

      Anyway, it is definitely nice when developers take the time to solve as many of the “little issues” involved as they can. Plenty of software out there that’s buggy and will just crash or glitch out. Can definitely be a breath of fresh air when shit works, or at least has errors that make sense. 😜

      • thingsiplay@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        9 hours ago

        Well, for starters, your application is confirmed to not be operating correctly;

        An error message does not mean the application didn’t operate correctly. Not able to write to disk, is a correct behavior with expected “errors”. The correct way to handle it depends on the application, but if it is about to show a message, then they could also incorporate more useful information that is already available.

        Another issue is parsing the log - while it’s not too difficult to check if it’s a disk related issue, accurately and successfully parsing the specific cause is maybe not so easy.

        Exactly why the developer should do it, not the end user. But if there is an error message, it does not necessarily mean they have to parse log files. In most cases most important and relevant information should be available already.

        It really depends, and depending on what the software does there are all sorts of odd little seeming issues that can make the whole process a headache.

        Maybe. But on the other side, it could also be a very simple process of adding a variable or a standard procedure. If there are discussions with 2000 pages about unclear error messages, then there is definitely something wrong. And the developers for this has to do something about it. Bringing attention to these issues is not a bad thing (although I don’t think Valve reads Lemmy posts).

        at least has errors that make sense

        I agree. At last…

        Edit: The point is, the application shows an error message that it could not write the file to disk. What file? I mean it would at least know what file, otherwise it could not check for not able to write it.