I agree, although I also see some usefulness: If your inner function names are sufficiently descriptive, you can write the high-level behaviour of the outer fu

I agree, although I also see some usefulness: If your inner function names are sufficiently descriptive, you can write the high-level behaviour of the outer function at the top, first to be read, to get a quick overview of what it does. Then declare the inner functions below that (this also requires that the inner functions must not have surprising side-effects). I've never seen or tried out code like that in practice, but it seems like it could work.