Not to disappoint, but it was just casually mentioned in one sentence, when offering arguments that Clojure doesn't have to compete against other languages like Scala; there doesn't have to be a winner. "Clojure doesn't have to 'win' to win. See, I'm a Go player, I'm not a chess player; I don't have to kill the other guy. I just need... marketshare."

(It'd be funny to take the metaphor too seriously and wonder if Clojure people are making subtle little moves, pretending just to be doing their own thing, culminating in the suffocation of the opponent...)

Incidentally, I can't tell if I miss CL's loop or not. It was my old standby. (That and ~{~} in FORMAT. Yes, I crossed to the darkside long ago.) But I find that with lazy sequences and so on, I can come up with elegant replacements, if I just think a little. I'm only unhappy when I use the loop..recur form, because relative to CL's loop, it spreads the looping machinery all over the place. I think some sort of simple cl-loop macro should take care of that pain point.

Not to disappoint, but it was just casually mentioned in one sentence, when offering arguments that Clojure doesn't have to compete against other languages like Scala; there doesn't have to be a winner. "Clojure doesn't have to 'win' to win. See, I'm a Go player, I'm not a chess player; I don't have to kill the other guy. I just need... marketshare."

(It'd be funny to take the metaphor too seriously and wonder if Clojure people are making subtle little moves, pretending just to be doing their own thing, culminating in the suffocation of the opponent...)

Incidentally, I can't tell if I miss CL's loop or not. It was my old standby. (That and ~{~} in FORMAT. Yes, I crossed to the darkside long ago.) But I find that with lazy sequences and so on, I can come up with elegant replacements, if I just think a little. I'm only unhappy when I use the loop..recur form, because relative to CL's loop, it spreads the looping machinery all over the place. I think some sort of simple cl-loop macro should take care of that pain point.

I once got randomly challenged by a pro.6 moves and I quit.Not sure if there's a language analogy that fits, there.

tayssir wrote:I'm only unhappy when I use the loop..recur form, because relative to CL's loop, it spreads the looping machinery all over the place. I think some sort of simple cl-loop macro should take care of that pain point.

One (possibly?) good thing about loop...recur is that you can't accidentally use non-tail recursion, because the compiler refuses to allow recur when not used in tail position.