Depends on your definition I suppose... but IMO adding a library absolutely does add to technical debt; especially if not well managed. TBH I can't be bothered getting into a long discussion on that subject right now; so I guess we can agree to disagree on that.
Anyway - the point is that some developers are more cautious than others; so we want to see tangible, quantifiable benefits before investing ourselves into a new library. As far as Tailwind is concerned I'm yet to be convinced 🤷
I am with David in this regard. Libraries don't add technical dept per se.
Technical debts are nothing else than poor code quality and poor architectural decisions. It is just a nicer way to tell the customer that the code base became a bit messy and some stuff needs to be refactored.
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.
How it adds technical debt?
What adds technical debt is to have a trillion lines of redundant CSS. Adding a library does not add technical debt.
Depends on your definition I suppose... but IMO adding a library absolutely does add to technical debt; especially if not well managed. TBH I can't be bothered getting into a long discussion on that subject right now; so I guess we can agree to disagree on that.
Anyway - the point is that some developers are more cautious than others; so we want to see tangible, quantifiable benefits before investing ourselves into a new library. As far as Tailwind is concerned I'm yet to be convinced 🤷
I am with David in this regard. Libraries don't add technical dept per se.
Technical debts are nothing else than poor code quality and poor architectural decisions. It is just a nicer way to tell the customer that the code base became a bit messy and some stuff needs to be refactored.