// This is not very handy because you might need to scroll down to find the last
// argument; you will also need to scroll down to determine whether the call to
// each is using currying
..only if your applied function is more than a page tall, which it probably isn't if it's inline? I think Ramda gets this right and yes, there are a few times where the order seems a bit less aesthetic but it feels more correct to me.
I do get where you are coming from and I do have to admit that even to me the entire reverse currying seems kind of alien…especially as someone coming from a very functional style where functions stay very short…
Unfortunately most JS code I work with is not written in such a functional style, so function bodys very often become larger than a couple of lines and in these cases having to search the argument somewhere a couple lines down does break the flow for me a bit…
It's the least problematic trade off I could find so far, trying to marry FP and procedural JS dev styles :)
Comments
I do get where you are coming from and I do have to admit that even to me the entire reverse currying seems kind of alien…especially as someone coming from a very functional style where functions stay very short…
Unfortunately most JS code I work with is not written in such a functional style, so function bodys very often become larger than a couple of lines and in these cases having to search the argument somewhere a couple lines down does break the flow for me a bit…
It's the least problematic trade off I could find so far, trying to marry FP and procedural JS dev styles :)