The example shows what's wrong: 1) bad error message. There error is explained in terms of some other machine, but not on the language level. 2) a zillion lin

The example shows what's wrong: 1) bad error message. There error is explained in terms of some other machine, but not on the language level. 2) a zillion lines of useless stacktrace information: I don't want to debug the REPL, but the wrong call. The stacktrace also lacks argument information. Generally I would hope for a 'live' backtrace. > Most of the time you're working from the REPL inside your editor anyways so the iteration loop is much, much better than any other language's. Any other language, but not compared to those who have a similar or better REPL or debugger. Which is a zillion. > Rebooting a program and losing state is always worse than error messages taking a bit longer to understand at first. Not sure how that is related...