Hacker News Reader

Comment by solardev | Hacker News Reader

Ramda was a hellhole I hope never to use again. We spent a year trying to learn it, finding it unreadable every time we went back to it (originally added by an outside contractor). Eventually we decided to give up, ripped it all out in a week and went back to lodash and never had an issue again.

Ramda code was just impossible to read and made every 5-min job take hours or days... not worth it, no matter the ideology.

View on HN

I have the complete opposite experience. Ramda is so much more consistent than lodash/fp.

I think your issue has more to due with functional programming in general than rambda vs lodash. It’s not for everyone but personally I really enjoy it.

I don't mean lodash fp, I mean plain lodash. We just rewrote everything into noob style that was infinitely easier to read and also made the code much more concise. The ramda stuff was buried like four levels of abstraction deep and we were able to replace them usually with one-liners.

I worked on a team that used it heavily, the lifecycle went like this. I joined the team and found it hard to read and understand, I learned it deeply, it became really easy to understand and made sense and I kind of liked it, the old people on the team who chose it left, I had new hires join my team, I found my self in the position of having to see how it affected their experience onboarding, I realized it was just kind of more trouble than its worth, we removed it later when we had the opportunity.

Reply on news.ycombinator.com