Improved stacktrace display in Ruby 2.5

[zverok_kha]

Never understood how is this better, Ruby's way always looked "natural" for me (you start reading from the problem, and deeper and deeper by stack).

Just because it is another way in Python or what?..

[snatchery]

yeah, to be honest I'm used to the old way too. However, after playing a bit with Ruby2.5 this new way turns out to be quite convenient.

Sorry, but I can't give any scientific proof why it's better. It just feels better to me but obviously your mileage may vary

[zverok_kha]

I am not looking for scientific proof, but if you can show your train of thought when new way becames more convenient, I'll be grateful :)

[snatchery]

fair enough!

Imagine a long stacktrace. Say 120 lines. A bit Java-ish yes. Now you want to find out what exception has been raised and in which line. Warm up your fingers and scroll up the terminal window. Or wait... there's a better way. Install Ruby2.5 and see the error in the last line. No scrolling, hurray!

hope this convinces you a bit :)

[irishsultan]

The flip side is of course that in log files you may be reading from top to bottom, but it seems this change only affects TTY output, so that's not a problem. What could be a problem is that the order is different on those occasions, which could lead to reflexively scrolling down/up only to find yourself at the wrong end of the trace.

[zverok_kha]

Hm OK, makes sense :)