On becoming Ramda 1.0

[skaushik92]

I've used Ramda for personal and professional projects over the years and have truly appreciated it as a contributor to a strong foundation for code readability and maintainability.

Given how relatively stable this package is for the vast majority of the people, I think establishing a roadmap to 1.0 would make it clear to the community what the maintainers consider the state of Ramda to be.

This previous post on Ramda's potential to go to 1.0 indicates there was some initial thoughts on this over 5 years ago, as well as arguments in favor of the bump. It looks like the effort subsequently went into triaging issues, or other involved tasks, which may have exhausted the efforts of the core contributors and maintainers.

I'm not saying that no further work needs to happen to get Ramda to 1.0, but I think the last 5 years of adoption have shown that ramda represents a stable API to incorporate FP into projects, and ongoing improvements (like those within the TS ecosystem) can be made without necessarily tying it to the 1.0 release.

I appreciate the high quality bar the mantainers and contributors have that has made this project flourish, but I think we shouldn't let seeking perfection mean not getting to 1.0.

Would love to hear any feedback on this, and I'm more than willing to jump in and help out to contribute to any necessary milestones to get this to 1.0.