Albin Jose@suppo.fi to Programmer Humor@lemmy.mlEnglish · 2 years agoUnbelievablesuppo.fiimagemessage-square62fedilinkarrow-up11.1Karrow-down135
arrow-up11.06Karrow-down1imageUnbelievablesuppo.fiAlbin Jose@suppo.fi to Programmer Humor@lemmy.mlEnglish · 2 years agomessage-square62fedilink
minus-squareTunaCowboy@lemmy.worldlinkfedilinkarrow-up65arrow-down3·2 years agoHave you considered learning how to read a stacktrace?
minus-squareZeroCool@feddit.chlinkfedilinkEnglisharrow-up48arrow-down1·2 years agoJokes on you, I don’t even know how to read.
minus-squareerogenouswarzone@lemmy.mllinkfedilinkEnglisharrow-up17arrow-down6·2 years 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·2 years 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·2 years 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
deleted by creator
There be dragons! Sounds like a good way to get passwords/secrets logged.