[X-Istence]

There is a certain amount of Java stuff I have running at $work as well, and the one I really care the least about is Jenkins, at least it isn't executing random code from the web.

The one that has me worried way more is all of the Android build tools. I've had random crashes happen in them and there is no good way to debug the issue. Java throws stack traces that if printed would cost you a ream or two of paper and sometimes you get crashes in something completely unrelated.

Ugh, there are many things I wish for, but Java no longer existing is probably one of my biggest wishes.

[andrewvc]

A stack trace is a stack trace in any language. It's the app developer's responsibility to provide a useful error messages after catching an exception.

This is CS 101, GiGo

[kbolino]

Not all exceptions are caught, and not all caught exceptions can have useful error messages. Try to figure out the cause of an SQLException in code and you will quickly realize it is an exercise in futility. To top it off, you are at the mercy of the implementer, who often seems to choose the most cryptic message possible.

Sometimes, all you have is a stack trace.

[pserwylo]

Is it the JVM throwing incomprehensible stack traces?

Or is it the android SDK throwing slightly less but still uselss stack traces?

I often see the later, which is just poor error/exception handling by the developers. I very rarely (sometimes, but not enough to get annoyed) see the JVM printing out stack traces.

[taligent]

No offence but if you don't understand how stack traces work and why it isn't a "Java" wide problem then no offence but you really are in no position to comment.

It really isn't that hard to understand.

[kbolino]

Just because you can read the stack trace does not mean it isn't a chore.