As a new user, it is way more useful. As an old user, you skip right past it. Every Python exception tells you > Traceback (most recent call last): Which is

As a new user, it is way more useful. As an old user, you skip right past it. Every Python exception tells you > Traceback (most recent call last): Which is a similar boilerplate statement. Except less useful to newcomers. And if you doubt the need for newcomers to understand that stack traces and compiler errors are useful, then take a look at new user questions on StackOverflow - it's incredible how many of them flat out don't include that information. This kind of thing makes it way more likely the user recognises this is something useful, and better than that - makes it way more likely they can apply that information and solve their own problem. > Besides, isn't a bug exclusively something that breaks at runtime? I mean, it would be a bug if the type checker hadn't caught it. The runtime distinction seems completely arbitrary when we are talking about tools take take runtime errors and make them impossible.