Hello developers!! In this part of the series, we will discuss techniques to work with function in Javascript called Currying.
What is Cu...
For further actions, you may consider blocking this person and/or reporting abuse
I understand, but variable naming was not my concern. The point is that most of the time this pattern is just used for the sake of currying itself i.e
a => b => c => //imperative code with a, b and c anyway. In which case it's only easy to write, not read - a reader (like me) can be left with "yes but why??"It's already arguable that we need both
multiplyandmultiplyByTwo. Surely there are valid use cases out there, especially in term of function factories, I just don't see many of them in my experience.Honestly speaking, I see the
b => a => a * bpattern to be needlessly terse. Very rarely do I see that pattern (and sometimes, currying itself) serve any practical purpose other than trying to appear "functional". Just my 2c though, to each their own.Awesome input.
Thank you!!
Great article. Thanks for sharing.
I'm glad you find it useful
Feels like currying is a kind of crying
What makes you feel that way? I’m an avid proponent of currying, so I’d like to hear the point of view from the other side as well