Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ramda vs TransducersJS (for example code) #5

Closed
ivan-kleshnin opened this issue Feb 22, 2016 · 2 comments
Closed

Ramda vs TransducersJS (for example code) #5

ivan-kleshnin opened this issue Feb 22, 2016 · 2 comments

Comments

@ivan-kleshnin
Copy link
Contributor

Your opinion? Ramda is also compatible with transducing protocol and is more popular / universal.
But I should mention I have no experience with TransducerJS. Any benefits you're aware of?

Here basically I propose to consider next options:

  1. Rewrite examples with Ramda instead of TransducerJS
  2. Mention Ramda as an alternative option

IMO: we should prevent people from getting an impression Medium is somehow bound to a specific transducing library. I can make a PR for any of this if you care.
@ivan-kleshnin ivan-kleshnin changed the title Ramda vs of TransducersJS (for example code) Ramda vs TransducersJS (for example code) Feb 22, 2016
@bbarr
Copy link
Owner

bbarr commented Feb 22, 2016

This is a great point, and I agree with both proposals. I will look into this with my next batch of free time, though PR's are always welcome :)

@bbarr
Copy link
Owner

bbarr commented Jul 19, 2016

Added reference to Ramda in 924cb18

@bbarr bbarr closed this as completed Jul 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bbarr @ivan-kleshnin