Functional programming in Javascript is an antipattern
Alex Dixon

Functional programming isn’t an on/off switch you can do as much or as little as you wish.

My view is that you should take functional programming as far as it’s comfortable to do in Javascript, but no further. Whenever I’ve seen tutorials of people trying to write JS like it’s Haskell it always looks awkward and I doubt the benefits outweigh the costs.

Using more than one out of Ramda, Lodash and Immutable is asking for trouble and from my experience Immutable is slow and unwieldy at the best of times.

I love Clojure, but even so I couldn’t imagine trying to transition my team to Clojurescript. I think you explain the upsides well, but there is a huge retraining exercise to get people up to speed with a non C like language, coupled with the additional build steps and added complexity of debugging transpiled code. I think a lot of people have the scars of switching over to Coffeescript and then finding they had a codebase in an obscure language which had been abandoned by the hipsters.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.