Basically, the logs exist for exactly this purpose. Just how it works.
it is wild for someone to say this immediately after saying “actually they can’t display the error because it’s too hard” and somehow not realize in the middle of typing how ridiculous it is trying to square those two claims.
ReptilianCleric@lemmy.zip 11 hours ago
Yes, and will outputting the log directly to screen help to make the error any less confiding?
And writing code that includes robust error catching and handling is simple, then?
thingsiplay@lemmy.ml 10 hours ago
No one asks to output the naked log line. There are a few more information that could be presented in a more readable and useful manner in a message box. Error messages are meant to be helpful, not to annoy without knowing what happened.
Even if you are right and the log contains the answer, why not trying to make more helpful Error messages? Does it hurt you?
ReptilianCleric@lemmy.zip 10 hours ago
I have nothing against helpful error messages, please understand; just pointing out this issue is not a trivial matter. It’s not like somebody is doing this just to intentionally annoy you, after all.
¯\_(ツ)_/¯
thingsiplay@lemmy.ml 9 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.