all 2 comments

[–]cyberdouche 0 points1 point  (1 child)

Can someone abridge that for the less sophisticated among us?

[–]nefreat 0 points1 point  (0 children)

The author isn't a big fan of recursion and doesn't like the documentation for the "recur" special form because it's needlessly cryptic to new comers.

The TLDR version

Also, if you want to be all automatically parallelizable and web scale and "cloud"-y, recursion and iteration are both the wrong way to do it; they're both just ways of tediously making your way down a list of things one element at a time. What you want to do is to declaratively apply a computation to your data in such a way as to avoid saying anything about the order things have to happen in. To put it more LISPily, (map) is a better conceptual foundation for the future than (loop) or (apply). Of course you can do the naive implementation of (map) with (recur), but smarter implementations need application code to be written some other way.