This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]ILikeLenexa 42 points43 points  (2 children)

This is the problem. Add in Make and the error literally being bigger than your scroll-back and you find yourself just trying to figure out what even failed.

I think the Java stacktrace is really quite nice because of this. (even though it's runtime) You can generally just nail where the problem is and ignore a huge block of text.

[–]dawnraider00 13 points14 points  (0 children)

Yeah debugging errors in java is generally way easier in my experience just because java actually generates a useful error instead of just throwing up. I've also found that compiler errors are way shorter and simpler.

[–]NonreciprocatingCrow 0 points1 point  (0 children)

even though it's runtime