These are chat archives for ramda/ramda

27th
Jan 2015
Scott Sauyet
@CrossEye
Jan 27 2015 02:56
@igiaever: We have so far done nothing to integrate with the various immutable container types. Some things might just work, if for instance a Mori immutable list type contains a map method that accepts a function, we'll call it, and call back to that function But we will not return a new Mori immutable list in response. I'd be interested in seeing how we might do that. And it might well be related to the transducer work that seems to be on a short hiatus, but will probably restart sometime soon.
Regarding the doc changes: The plan was to reintroduce the category filter soon after we put these out there. Someone will be on that soon. The Github link was to my mind a minor oversight. I don't know where the broken links are. I'll investigate soon. I'm looking forward to the tasks from @wildermuthn to make it easier to work with the docs. I'm hoping they'll make it easier to work with the docs on my new machine where somehing is still not not working correctly.
Victor Cottin
@Cottin
Jan 27 2015 09:02
have u guys tried https://github.com/lodash/lodash-fp yet? I'm afraid my co-workers will use it as an argument in the coming weeks to force away my beloved ramda in our project. Could you supply me with some arguments so I don't have to change? :)
Scott Sauyet
@CrossEye
Jan 27 2015 14:20
I haven't really tried it yet, but I'm anxious to do so. We're not much on marketing here, so even when I do learn it, I may or may not have substantive points for you. But there is one real reason to consider choosing Ramda or FKit over this new lodash offering: FP is our entire reason for being. The goal of our team all along has be enabled to create a useful functional library. Meanwhile, lodash's primary author, John-David Dalton had been on our issues list, critiquing our design decision, large and small. Now his new offering mimics those same design choices. So there is a real question of his commitment to the principles espoused by the library. Is lodash-fp just the result of some misplaced competitive streak? You will always know that's not the case for Ramda.
Nate Wildermuth
@wildermuthn
Jan 27 2015 14:57
@CrossEye I'm happy to help out with any front-end js documentation issues, like sorting by category.
Danny Arnold
@despairblue
Jan 27 2015 15:26

also regarding the new docs, I think I was able to operate the old one with just the keyboard:

  1. typing what I'm looking for
  2. using the arrow keys to select the entry I'm interested in
  3. rinse repeat

(2.) does not work anymore

Am I mistaken?

Scott Sauyet
@CrossEye
Jan 27 2015 16:27
@despairblue: we will definitely check into that as well.
Scott Sauyet
@CrossEye
Jan 27 2015 16:35
@wildermuthn Thanks. @saikobee has done the recent work and will, I imagine continue. I'm sure he'd appreciate help.
Danny Arnold
@despairblue
Jan 27 2015 18:16
@CrossEye thx :)
Jethro Larson
@jethrolarson
Jan 27 2015 20:50
After writing a bunch of getters to create an interface for a view of a model in some other archaic framework, I long for the simplicity of viewModel = pick(['foo','bar', 'baz'], model). Oh and I just discovered R.evolve, that's pretty rad. Then if you need to mutate some props it's easy transform them only as needed. You could use evolve to map data to html templates. I love this library <3
Jethro Larson
@jethrolarson
Jan 27 2015 21:54
I have a list of functions and I want to map them to a common arg. Is there a construct for that? map(flip(apply)(of(arg)), fns) seems like it'd work but it also feels kinda wrong.
Michael Hurley
@buzzdecafe
Jan 27 2015 21:57
ap(listOfFns, listOfArgs)?
so for one arg: ap(listOfFns, [arg])
Jethro Larson
@jethrolarson
Jan 27 2015 22:07
Cool. I looked at that but I was having trouble understanding how it worked. Got it now.