Chapter 5: example demonstrating associative example doesn't work about mostly-adequate-guide HOT 5 CLOSED

Hi! The paragraph below the example tries to point out that it's more complex than the compose written above. Perhaps, we should prefix compose with _ in those examples?

from mostly-adequate-guide.

That would make it more explicit.
I think the same should be done with this line: var reverse = reduce(function(acc, x){ return [x].concat(acc); }, []); use _.reduce to make it explicit that we take them from a library.

from mostly-adequate-guide.

Yeah, my current overhaul has to do with not relying on previous (or missing) definitions of functions. I'll try to find time this week to use lodash-fp or ramda as much as possible

from mostly-adequate-guide.

I really appreciate your book as I am relatively new to functional programming, it helps to make my code more readable and declarative.

One interesting feature that might be nice to add within your book, is how you integrate functional paradigms with a framework like Mithril (my favorite) or React or other libraries like paths-js or D3.js for charts, i.e. use cases/real world examples

from mostly-adequate-guide.

Thanks for the suggestions! For the compose confusion, I'm going to open an issue to replace as many custom functions with _ so we know where they're coming from and close out this one.

from mostly-adequate-guide.