A lot of issue I have with a typical stacktrace is the signal-to-noise ratio -- a lot of information is plainly irrelevant most of the time when the offending code happens in my application (or code "space"). This is one issue, but not the primary one.
Small fixes, even typographically speaking, could help immensely. Some of these are not feasible in a text-only environment; it would be nice to provide a stacktrace that considers both visual and semantic improvements.
For now, nothing is particularly actionable, so this serves as a marker for future endeavors.
A lot of issue I have with a typical stacktrace is the signal-to-noise ratio -- a lot of information is plainly irrelevant most of the time when the offending code happens in my application (or code "space"). This is one issue, but not the primary one.
Small fixes, even typographically speaking, could help immensely. Some of these are not feasible in a text-only environment; it would be nice to provide a stacktrace that considers both visual and semantic improvements.
For now, nothing is particularly actionable, so this serves as a marker for future endeavors.