Hacker News Reader

An infinite loop is not the most frequent type of non-termination. Crashing is.

When your "config" fails to load halfway through its interpretation because of a KeyError, ValueError, NullPointerException, "null has no method <whatever>", you see some of the downsides of Turing-completeness.

View on HN

Crashing is termination; the reason it's tricky is that we often treat programs as having return type "Foo" when they actually have return type more like "Foo | Stacktrace".

(Sometimes it's easier to do theoretical work by replacing crashes with infinite loops; but that's only because it's impossible to do the converse ;) )

given your argument, it seems your gripe is with object orientation rather than with turing-completeness.

Rather, with dynamic languages used for config files. I could use Lisp or Lua for the example, but they are not as recognizable in this role.

Reply on news.ycombinator.com