However, actually trying to figure out what the hell the code is doing in pointfree style is an order of magnitude (or greater) more difficult.
This is a maintainability nightmare, no thank you.
I found the pipe() example to be more readable. BUT I would not think through the implementation detail, auto-currying functions so that I dont have to etc.
FWIW I love Scheme, but had not thought about these concepts for years. Seeing them in a new context, Currying and partial application, I can see how I could write some stuff that would trip up other JavaScript programmers. Not because I am a better programmer, but because I have habits from a differemt programming style.
Came here to say pretty much just that. The original lambdas that got "fixed" I could read very easily. The pointfree style I could figure out but it took a few extra cycles to do so. No thanks. It's neat that you _can_ do this but anyone coming upon it who wasn't the author would have to burn a lot of mental calories figuring out what the hell was going on.
Anyway, I'm advocating to use it with caution, not in a "pointfree all the things" manner.