• SavvyWolf@pawb.socialEnglish
    1·
    10 months ago

    Willing to bet that the backend that they are using doesn’t actually give any useful error messages.

    • GarytheSnail@programming.dev
      2·
      10 months ago

      Would they surface that to the user anyway? That’s something to log, not to tell the client that xyz service failed because of error 123.

      • Johanno@feddit.de
        2·
        10 months ago

        I hate this attitude. Yeah don’t give the user stacktraces on error but if you give it a meaningful headline and go in detail, experienced users will be able to deal with the problem if possible. If you go Microsoft-error of mystic ways you will have people Google “unexpected error e34566xce” and they will see that it has 10 possible reasons so you don’t know what even went wrong.

  • PeriodicallyPedantic@lemmy.ca
    1·
    10 months ago

    Tbf if the client fails to reach the server, there isn’t much more detail they can provide. At least it brings a little levity