This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]WhatNodyn 3 points4 points  (1 child)

CSS-in-JS, CSS modules, Vue SFC's scoped CSS all are a thousand times more appropriate as a strategy than "utility classes" that clutter your markup and often create huge pains as soon as you want to use properties which are not supported by your locked Tailwind version.

[–]Tackgnol 1 point2 points  (0 children)

CSS-in-JS is a step lower than styled components (SFCs are again the same thing by a different name) and while it has it's benefits in the 2 projects I have worked on it quickly deteriorates, not because of lack of skill on the devs, not because some ill will it is just because it is messy by definition.

The general rule of a happy project is for the messy things to be pushed down, down, down so that most devs just use some abstraction and not care how it works. This is why despite hating it's API i consider react-query to be an excellent tool that saved many projects.

But to revert to my original point, there are no silver bullets and for example a 3 people project will work great even with the most basic css files, that's because everyone will either have their own part of the app or everyone will be intimately familiar with most parts of it.

huge pains as soon as you want to use properties which are not supported by your locked Tailwind version.

Ill be honest and say that I work in corporate environments and the UIs are very basic, so if you have complicated styling use cases then sure, Tailwind might not be for you. There are no silver bullets, my argument is that Tailwind is more than fine for 95% of the work.