Albin Jose@suppo.fi to Programmer Humor@lemmy.mlEnglish · 1 year agoUnbelievablesuppo.fiimagemessage-square53fedilinkarrow-up11.04Karrow-down134
arrow-up11.01Karrow-down1imageUnbelievablesuppo.fiAlbin Jose@suppo.fi to Programmer Humor@lemmy.mlEnglish · 1 year agomessage-square53fedilink
minus-squareTunaCowboy@lemmy.worldlinkfedilinkarrow-up64arrow-down3·1 year agoHave you considered learning how to read a stacktrace?
minus-squareZeroCool@feddit.chlinkfedilinkEnglisharrow-up46arrow-down1·1 year agoJokes on you, I don’t even know how to read.
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-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.
Have you considered learning how to read a stacktrace?
Jokes on you, I don’t even know how to read.
Damn, got us good!
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.)
deleted by creator
There be dragons! Sounds like a good way to get passwords/secrets logged.
deleted by creator