Scott Sauyet

A quick meta-discussion comment first: Here on Ramda, and in most GitHub communities I've seen, we act differently than we might on, say, StackOverflow, where the goal is to get...

@KayaLuken: Sometime soon, after giving it more thought, I will consider opening a new issue regarding the `as-with` functions, but I would like to respond to your suggestions: > My...

@ramda/ramda-core: I'd love to hear any feedback on the ideas here -- not my `as-with` stuff on which I still want to stew a bit before deciding whether to even...

@semmel: While that is a fine example of the use of `concurrent`, I would hesitate to actually use it in documentation, as people already think of concurrency when they see...

@semmel: You're absolutely right. There needs to be a real discussion about the names. I just want to make sure that people are on board with the idea before someone...

@KayaLuken: We'll figure out the names. I have no problem with `each`. `forEach` can just go to hell! :smiling_imp: While `forEach` itself is pure, its only purpose is to do...

The first two weeks of August, I simply don't participate; my vacation time is sacrosanct. I missed this one entirely. It makes sense to me on a quick read. @dustinws:...

Hmm, that's unfortunate. It might be possible to fix, using `Object.getOwnPropertyDescriptor` and `Object.defineProperty` in place of the [relatively simplistic code][as] we have now. I have no idea how this might...

A first pass (untested except for the included scenario) is at https://goo.gl/hiJ9yD . I wouldn't be surprised if there are significant problems with it.

Probably. I often use `propEq` as my demonstration that although it's usually clear enough what order to put parameters in, once in a while, it simply seems to be an...