Albin7326@suppo.fi to Programmer Humor@lemmy.mlEnglish · 1 year agoUnbelievablesuppo.fiimagemessage-square63fedilinkarrow-up11.1Karrow-down134
arrow-up11.06Karrow-down1imageUnbelievablesuppo.fiAlbin7326@suppo.fi to Programmer Humor@lemmy.mlEnglish · 1 year agomessage-square63fedilink
minus-squareerogenouswarzone@lemmy.mllinkfedilinkEnglisharrow-up17arrow-down6·1 year agoIt is 2023 my brother in christ! We deserve better error outputs than a stack trace. Tell me what line in my file caused the error, Tell me the values of the variables involved, Then you can have the stack trace. Why are we pretending like these error messages are acceptable in 2023?!
minus-squaresegfault@lemmy.worldlinkfedilinkarrow-up5·1 year agoso said EVELYN the modified DOG (This is not just a Zappa quote, but an actual error description from the Small Device C Compiler.)
minus-squaretrash80@lemmy.dbzer0.comlinkfedilinkarrow-up3·1 year agoWell, everyone knows what that means.
minus-squarepingveno@lemmy.mllinkfedilinkarrow-up3·1 year ago Tell me the values of the variables involved, There be dragons! Sounds like a good way to get passwords/secrets logged.
minus-squareYawnder@lemmy.ziplinkfedilinkarrow-up3·1 year agoI can't tell if that was sarcasm or not. If it was, you got me. If it wasn't, then that's quite a big lack of understanding of what's actually happening.
It is 2023 my brother in christ! We deserve better error outputs than a stack trace.
Why are we pretending like these error messages are acceptable in 2023?!
(This is not just a Zappa quote, but an actual error description from the Small Device C Compiler.)
Well, everyone knows what that means.
There be dragons! Sounds like a good way to get passwords/secrets logged.
I can't tell if that was sarcasm or not. If it was, you got me. If it wasn't, then that's quite a big lack of understanding of what's actually happening.