4 ms·

Logs are useful because they give an idea of what was going on when a particular failure happened. More context than a call stack. > Pretty disappointed with t

Logs are useful because they give an idea of what was going on when a particular failure happened. More context than a call stack. > Pretty disappointed with the actual post. I am as well. What the author describes isn't new or novel, it's been in Windows in the form of ETW since the early 90's. And Windows wasn't the first OS to get it. Had the author taken a serious System/OS class he would have known. You can't build high performance applications without using some scheme similar to what the author describe.

joshka 5y ago
It sounds like the thing you're missing is the concept of "context" not "logging". If you frame the question as what information do I need to diagnose a problem with this code if (and only if) it fails, and likewise what info when it succeeds do you end up with logging as the best solution? Probably not - events seem to be a better perspective on this. >Had the author taken a serious System/OS class he would have known. I'm guessing the author probably did so - this comes across as fairly ascerbic btw.