These are chat archives for ramda/ramda
quick question on ramda/ramda#1869
Why does ramda advise against using promises?
I'm not sure what the official reasoning is, but here goes my interpretation.
Their not pure because they eagerly evaluate and the A+ api makes composition awkward because
.then is both
Promise semantics are an example of the difference between easy and simple. Promises are easy to use initially but there are many ifs and buts when using the API. Meanwhile a Task or a Future is bound by Monadic laws that makes them perhaps harder to use initially but simpler in the sense their behaviour is limited to a relatively small and shared set of laws.
Simplicity leads to consistency which makes composition easier.
That said, you can use Promises with ramda without pipeP/composeP quite easily