Ramda: QUESTION: is this properly maintained?

[woss]

Hi, i want to say i love the this lib and I would really love to use it longterm but amount of the PRs and issues is worrying for a project like this.

Is it actively maintained? Do you need help? i wouldn't mind sponsoring you if you choose to do so.

[CrossEye]

I'm not sure what you mean by properly maintained. It is actively maintained in the sense that new issues are generally reviewed and commented on, sometimes acted on, within a few days. Issues/PRs do tend to stay open for a long time, and there is no real process for cleaning up behind ourselves. We need to get better at this.

We still have not reached version 1.0 years after we probably should have. We do not have a timeline or any real processes, and we're slow to post releases.

However, it is widely used, with nearly 20K GitHub stars, and nearly a million daily NPM downloads. People are finding it useful. Clear-cut bugs tend to get fixed quickly. It has claimed the space of the leading pure functional utility library for JS.

Ramda started as a hobby project. @buzzdecafe and I wanted to know how far we could take an FP style of coding in Javascript. It was a quiet little project known only to us and a few friends when it got picked up and used in a Frontend masters course, which convinced us to start talking about it. The response was stunning, and we clearly had hit a nerve. We've been joined by many talented developers since, and met some amazingly smart people who have helped make the library much stronger.

Many people are using it, and I think it's working for them. But there is a tremendous amount we could do better.

If you want to contribute financially, we did set up an Open Collective account a few months ago, but we're not really sure yet how we will use that money. Most helpful would be contributors willing to take on some of the burden of turning this ragtag but useful library into something more professional. Any advice along those lines would be welcome, but even more welcome would be help from people eager to make that happen.

[woss]

thank you for the long answer. I became the backer and hopefully contributor one day. i would really love to see this project hits 1.0 for many reasons.

First would be from selfish reasons because i orchestrated a really complex implementation of a proof verification and generation on ramda functionality.

Second, I think if implemented in TS many people would be using it and help you (maybe me as well) maintain parts of it since the types would be autogenerated.

Third, there are little resources in forms of tutorials out there, yes there are few old ones, (not much changed though) but I believe it could be more, and I will share and write about it when I get a better grasp of it and then share the actual code ( all the stuff I'm doing it's open source) which will help people to understand HOW to use it.

Thanks again for the response :)

[CrossEye]

There's little chance of Ramda switching implementation to TS. See the reasons and discussions in #2976. But we are looking at how to improve the TS support.

I'd suggest that most of the Ramda tutorials (at least those since 2015) are probably still fairly accurate. And, as a library, it will never have the sort of documentation that framework have and need. There is room -- plenty of room! -- to improve the documentation. And tutorials are among the best ways to do that. That is one way that you could easily help. Write a tutorial about some part of Ramda that interests you but you don't think is well-documented. Tell us about it and we'll add it to the wiki. Or simply add a wiki page with it if you don't want to host your tutorial somewhere else.