[Melbourne-pm] Stack traces

Sam Watkins sam at nipl.net
Tue Feb 12 18:02:19 PST 2013

On Wed, Feb 13, 2013 at 10:50:56AM +1100, Toby Corkindale wrote:
> I've seen Java stack traces that are easier to figure out than this.

<snip 646 line stack trace>

Frankly, I think the solution is - don't use all that ridiculous bloated crap!
Keep it simple.  If you can write it in one line, do so;
Don't write 20 pages when 1 will do.  Don't use bloated 3rd party modules,
only if they are as clean and simple as possible for the necessary task.

Read "The Practice of Programming" ...
Chant "Simplicity, Clarity, Generality" ...

This is my personal opinion only, and does not necessarily represent
the official stance of the company for which I work.  Unfortunately.

On many systems, in normal languages, with normal libraries, a stack trace
like that would indicate stack overflow due to unbounded recursion...
(is that perhaps what happened?)

More information about the Melbourne-pm mailing list