Monster traces still contain useful info, though perhaps the way they are rendered by most loggers, IDEs, etcetera could use some help. At some point that stack trace devolves more into a blueprint for a debugger or VM inspector to load then for something a human ought to be scanning.
I also like python's style more (a python stack trace inverses the ordering compared to a java stack trace - the deepest method is listed LAST, vs. java where its listed first). The same can usually be said for causality chains: If an exception bubbles up so far that it gets handled via error dialog / logging (the right kind of logging, i.e. at the container level, not the wrong 'catch, log, forget' anti-pattern), and you're actually looking at it to try and figure out what happened, looking at the deepest item in the causality chain is usually more enlightening. So, yes, giganto-traces are an annoying nit, but it only takes me maybe 20 more seconds to delve through it and find the appropriate location to look, I definitely want all of it in case its more complicated than that, and at least in theory I think if this grows into too much of a problem better ways of rendering the trace could be written. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
