Why I never re(re(re(re(re(curse)))))

In 40 years of active programming I’ve never used a recursive function. I don’t see why you’d want to GUARANTEE problems. I know the Turingian theorists and Computer “Science” classes advise recursing everywhere, which is an added reason to avoid it.

In the AI era, text witch hunters search for em-dashes. In coding the witch sign is infinite recursion, as seen at the surface in crap like this or this.

Tried Substack just now, and Firefox spewed this long printout, catching the recurse with an interesting message at the end. Hey developer! You can provide a way better UX than this by providing your own error handler.

Interestingly the ‘rate of change’ resembles the text examples above. It starts linear then recurses over a shorter and shorter loop.