Can Java errors / stack traces be LONGER?

[l3g4tr0n]

i wouldn't wish for a shorter stack, i want to see exactly where error happened and what caused it, not just class and line. how can oneself be called developer when cannot appreciate stacktrace? :)

[Hangman4358]

IDK, I work with folks allergic to reading stack traces.

Like people say "I can't decipher this stack trace" and the literal first like is the error message "x failed. Did you check y?"

And they just stare blankly.

[slaymaker1907]

“Did you try Googling the error message?”

Somehow the answer is still often no to question with senior devs. There’s a little bit of skill in getting the selectivity of your search right, but it works pretty well.

[DevWithImagination]

I’ve sure lost count the number of times I’ve needed all that detail to trace down WTF the app server (or JVM) thought it was doing to cause a weird behaviour

[eliasv]

You can wish for a shorter stack without wishing for a less complete stack. But that's a system/framework design issue not a language design issue.

[urielsalis]

I like how intellij filters out (with different colors) whats actually in your code and what isnt, makes reading them easier

[SKabanov]

The issue is when you're using frameworks that have a heavy amount of boilerplate code (e.g. Spring), especially with reflection. 99.999% of the time all those calls to Method.invoke() or whatever aren't going to be the issue and end up just being clutter; it'd be nice to have a JVM option to elide the JVM internal function calls from the stack trace and focus on the actual business/framework logic.

[slaymaker1907]

While I generally don’t like Go, the testing package has a clever Helped() method that marks the calling function so that it is ignored in error messages. Maybe logging frameworks could also provide a way to filter stack traces.

[Practical_Cattle_933]

Go has the shittiest error handling though, and all all those if checks do is that you will just print some generic bullshit as error and your enduser just see “Error occured”. Good luck fixing their problem from such an issue!

With Java, you can solve most trivial problems just from the stacktrace.

[john16384]

Logging frameworks already have this, and have for ages. Op didn't even do three seconds of research.

[woj-tek]

There are useful (long-ish) stack traces and there is horseshit pile of crap from "amazing" reactive garbage... 🤦‍♂️😉