4 ms·

I considered Ramda at my last company for a hot minute, but ultimately decided it was too opaque to be a reasonable decision. We ended up using lodash for a lit

I considered Ramda at my last company for a hot minute, but ultimately decided it was too opaque to be a reasonable decision. We ended up using lodash for a little while, but in reality used like 2% of lodash, so I ripped it entirely out in favor of our own small utility collection with really sound typescript typing. I think, in any project, it’s best to repeat yourself more, and patiently watch to see which abstractions actually emerge.

fendy3002 3y ago
> but in reality used like 2% of lodash, so I ripped it entirely out in favor of our own small utility collection with really sound typescript typing. Which is lodash already, wonder why your team feels like the needs to make and maintain a new component for that is valid. Furthermore, lodash is somehow optimized for it's purpose, so the custom implementation may be inferior. I never aim for file size but AFAIK lodash support tree shaking which is good enough.