I like your shaded answer, because I think this is our daily struggle as developper: do we invest time in "absorbing" a new entity (e.g. library), even if it does not fits 100% our needs, and work it out around, or do we put some time to create our own.
It's always a matter of trade offs and bet. The best product is where you made the best medium-long term choices in term of tools.
I would personnaly go for it if I know this is the kind of tool that will serve my needs a lot of times (like I did with my service worker library). This is a bet, maybe service workers will be superseded by another tech, but I feel in my gut it will be worth for now.
Interesting point about choices, yes especially in frontend world, it is never easy to predict, but it should be relatively easy to design for a couple of years ahead, even though you're not sure about the choice of lib/framework/tool
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I like your shaded answer, because I think this is our daily struggle as developper: do we invest time in "absorbing" a new entity (e.g. library), even if it does not fits 100% our needs, and work it out around, or do we put some time to create our own.
It's always a matter of trade offs and bet. The best product is where you made the best medium-long term choices in term of tools.
I would personnaly go for it if I know this is the kind of tool that will serve my needs a lot of times (like I did with my service worker library). This is a bet, maybe service workers will be superseded by another tech, but I feel in my gut it will be worth for now.
Interesting point about choices, yes especially in frontend world, it is never easy to predict, but it should be relatively easy to design for a couple of years ahead, even though you're not sure about the choice of lib/framework/tool