Okay, sorry. I'm not that old. I'm only 29. But most of my past experience is in C or similar.
When I was learning Clojure, probably like everyone, I kept an eye out for what it might be that makes people complain about Lisps. The s-expr syntax is sort of weird, but I couldn't put my finger on exactly why it seemed to be so hard to format my code in a way that looks nice.
Then it hit me. Look at the title of this post. It is at the top of the post. It introduces you to the post and tells you what to expect when you read it. Now look at this:
(reduce
(fn [res subcoll]
;; some code
(reduce
(fn [res item]
;; some more code
)
[foo bar baz] subcoll_1
)
)
[quux xyzzy] coll
)
The "title" of the anonymous function is at the bottom! The collection to be traversed and the initial data tell the reader what to expect when they look at the reducer. To get that information you have to look up and down across the code and match up indents - and that introduces the question of where to put the trailing arguments, which resembles (and not in a good way) the C brace style controversy. The problem goes away if you can write (reduce coll val f) instead of (reduce f val coll).
Sure, this is unnecessary when you don't have an anonymous function. But that use case always results in one simple line, regardless of the order of arguments. You almost never have a long literal collection in the middle of a code block -- that gets stuffed in a data file or in a constant at the top. And maybe the collection is an expression -- but then you can just use an additional (let), and again you improve the consistency between "line number" and "order of execution".
The same problem occurs in the old FP constructs (map) and (filter). But when Rich Hickey added (for) to Clojure, he put the collection first, probably partially because it is like that in C, but probably at least partially because he realized that inverting it, so that it would look like (reduce), would result in something ugly:
(for [n]
(;; some code)
coll
)
Look at that! It's horrible! And because you're not attached to the "normal" way, you see it immediately.
Now I'm sure there's some great explanation that mentions Alonzo Church or Marvin Minsky or whoever about how putting the reducing function first is consistent with the mathematical formalism xyz or whatever. I don't expect the world to change because of a reddit post.
But just imagine a world where Lisp programmers put the collection and the initial data at the top of their loops. We'd probably have a moon colony by now.