DEV Community

Discussion on: "Too complicated, a library will handle it"

dylanesque profile image
Michael Caveney

I think it's appropriate to reach for a library when it solves a problem in a very standard way and is battle tested. I always go back to that thing that Kent C. Dodds said about making yourself feel the pain of a problem before you reach for a dependency or a library to solve it for you. But it must vary by problem type, right? For example, Moment.js takes away a lot of the pain of working with dates (provided the bundle size isn't too big). On the other hand, how many React devs reached for a solution like Redux for state management when the built-in state management tools and techniques (even before Hooks) were more than sufficient? This definitely is a case-by-case thing.