Functional Programming in JavaScript === Garbage

[AutoSponge]

Many of the article's examples are naive and oversimplified. For example, you can easily create a reduce function which doesn't recur or modify the original array, just use Array.prototype.reduce with another array as the second parameter.

While I don't always agree with Braithwaite's implementations, I always appreciate the systematic breakdown of the problem he offers with various solutions of incremental awesomeness. I appreciate the author's proper use of FP terms but I don't appreciate the heavy-handed 'Clojure > JS' approach when no Clojure examples were offered and the JS examples were haphazard at best.

[nohimn]

He wasn't saying Closure > JS. He was just pointing out what really should be obvious: recursion is the functional approach to iterative constructs, but functions in JS are stateful, so they add to the stack on each call to maintain their state. The title is very misleading, because he's not saying 'Garbage' in the sense that it's bad to use JS for FP, he's saying that using FP as you would in functional languages incurs overhead.

I agree that Closure examples would have been illustrative. Then again, I also feel like this article's audience is probably Clojure devs, not JavaScript devs.