Dmitri Zaitsev

> While it would certainly be possible to support both, as a matter of prioritization it would make sense for Ramda to work with types that match its basic philosophy,...

@CrossEye I have read your blog long while ago and really liked how it made clear some of ramda's advantages and it was what attracted my interest to it at...

> One of the things it does it distinguish 0 from -0. Indeed, this makes more sense than the weird JS native behaviour, but is it documented anywhere? > `x`...

Another useful notion of equality that is not even an equivalence relation would be `eqApprox` that would satisfy ```js eqApprox(0.1+0.2, 0.3) //=> true R.equals(0.1+0.2, 0.3) //=> false 0.1+0.2 == 0.3...

@donhatch > I have trouble taking native/A+ promises seriously, mostly due to its impossible-to-analyze behavior around automagically unwrapping thenables (I believe this is commonly known as "failure to be a...

@bergus >> Maybe start with some scary "then-able" surprises and move on to … > I would not recommend to start a tutorial with that. New users want to learn...

@briancavalier > it seems helpful for the API docs to emphasize map, et al. and group A+ / ES interop functions (i.e. then, catch, and finally) together and explain more...

Here are some basic usage examples: https://github.com/dmitriz/functional-examples/blob/master/examples/12-creed.js https://github.com/dmitriz/functional-examples/blob/master/examples/13-creed-async.js https://github.com/dmitriz/functional-examples/blob/master/examples/22-creed-traversable.js

Thank you @briancavalier for the explanation, I would have never guessed it is on the `creed.Promise` namespace. ;) It does not even show up in the REPL: ```sh > creed...

@bergus > That's the whole idea. The Creed Promise constructor can be used as a drop-in replacement for the native promise constructor. Hm... Then why not just use the native...