Unhelpful error from `rails test:system` brought this to mind, but there have been a few other topics in this forum that brought up “this stacktrace is too long / not helpful.”
There was also a comment that brought up that many folks mis-attribute errors to Bootsnap because it’s in nearly every stacktrace and they need someone to blame.
I’ve noticed a number of newbies over the years have emotional responses to stacktrace vomit. Long weird stacktraces full of framework details can be really scary! When I was first learning Rails (back in 2008, oh god) something similar made me put the framework down for a few months because I felt so defeated.
- more aggressive default stacktrace cleaning?
- more affordances for flipping between “focused” and “verbose” stacktraces?