These are chat archives for ramda/ramda
ramda_utils.jsor similar — which contains the kind of util functions that exist in the ramda cookbook, generally. obviously there’s plenty of overlap among projects, but at the same time not enough overlap to justify a single, ever-growing ball of mud collection that i’d include in any project. the question, what is the best way to maintain re-usability across projects, while still only “importing” (in the general, non implementation specific sense of that word) the functions i need into a particular project. on one extreme there is the node-esque “leftPad” philosophy where you package each function separately, but that approach feels wrong to me, mostly because functions do form semantically related clusters. on the other end, you could be forever curating a “date_utils” and a “math_utils” and so on, but resolving conceptual overlap, or moving functions from one module to another, etc, also seems like a burden. how do you deal with this?
sum $ sequence [(+10), (+20)] 10
foldl1 finalOperation $ sequence fs x