[kevinmgranger]

Not that I agree with how Go handles it, but the computer is not always better at it. It's a tradeoff, a compromise, or a catch-22.

If you use the full stacktrace, you could get 50 frames of irrelevant library code worsening the signal:noise ratio, hiding what the real issue is.

If you write your own context, then when it _is_ a problem with library code, you're hopelessly lost.

I think we need better tooling: the ability to add your own contextual information, to propagate errors explicitly but without boilerplate, and the ability to _choose_ the level of information you see afterward.

We have log viewers that can filter out by severity level, why don't we have a standardization for stack traces to let you filter to what you want?